Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fb978c81c7f4ba8bcbf59c27a001bc8c324da499c91099f0e987b957b8f3fcc5

Tx prefix hash: bff7e75acf0ffa7f620216d301dd93ec9e38037c0a45cd824f0ca0f1ed3c5c27
Tx public key: a617a800c6af36b1eb71fba857d52af2e9afcdbba03e2990fd4a9a21b4422930
Timestamp: 1759750264 Timestamp [UCT]: 2025-10-06 11:31:04 Age [y:d:h:m:s]: 00:118:01:12:27
Block: 1383994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84338 RingCT/type: yes/0
Extra: 01a617a800c6af36b1eb71fba857d52af2e9afcdbba03e2990fd4a9a21b4422930021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32bc706cbace864488296bb746e7f6fc0d61e1e141ce0505eb1512c2763a2663 0.600000000000 1872143 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1384004, "vin": [ { "gen": { "height": 1383994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32bc706cbace864488296bb746e7f6fc0d61e1e141ce0505eb1512c2763a2663" } } ], "extra": [ 1, 166, 23, 168, 0, 198, 175, 54, 177, 235, 113, 251, 168, 87, 213, 42, 242, 233, 175, 205, 187, 160, 62, 41, 144, 253, 74, 154, 33, 180, 66, 41, 48, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8