Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e72d3e7d3da132020a597dd9c1d3b4d310b2c47e1c2f41a1f5b07592f192753

Tx prefix hash: 455907dd1f21ce61b569439c5134fd32d251ae8d06ef87ce1ab6f6af56c9c023
Tx public key: fe906637fdc8abfdd6e3d770a39d4b2c48c1d2bb971e04b9a3edfd4c1b82ef9d
Timestamp: 1760461700 Timestamp [UCT]: 2025-10-14 17:08:20 Age [y:d:h:m:s]: 00:028:02:29:55
Block: 1389884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20128 RingCT/type: yes/0
Extra: 01fe906637fdc8abfdd6e3d770a39d4b2c48c1d2bb971e04b9a3edfd4c1b82ef9d0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb4a3c5170e43dc3436d5649ac51d16fce36f6b9754e73d09ef1bebf4945281a 0.600000000000 1878113 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": 1389894, "vin": [ { "gen": { "height": 1389884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb4a3c5170e43dc3436d5649ac51d16fce36f6b9754e73d09ef1bebf4945281a" } } ], "extra": [ 1, 254, 144, 102, 55, 253, 200, 171, 253, 214, 227, 215, 112, 163, 157, 75, 44, 72, 193, 210, 187, 151, 30, 4, 185, 163, 237, 253, 76, 27, 130, 239, 157, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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