Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5b2b221724684d5cfe235cf11c70dd74a53dbca882035601c5c94aed18b4fd9

Tx prefix hash: 86671f5fe1f6f4d972adbeff59296796eafb9558c26577e8d5e7fc4c4959e7eb
Tx public key: ffe264794d319eadd8de34f6c12d378ae15a8e98665d11e8045e4414b8b76954
Timestamp: 1765858009 Timestamp [UCT]: 2025-12-16 04:06:49 Age [y:d:h:m:s]: 00:006:06:49:39
Block: 1434605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4496 RingCT/type: yes/0
Extra: 01ffe264794d319eadd8de34f6c12d378ae15a8e98665d11e8045e4414b8b7695402110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbed5fd6b19c8e5fcf2df80a1e9df4f7078f63bcb683774cd2918e8598a91806 0.600000000000 1923396 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": 1434615, "vin": [ { "gen": { "height": 1434605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbed5fd6b19c8e5fcf2df80a1e9df4f7078f63bcb683774cd2918e8598a91806" } } ], "extra": [ 1, 255, 226, 100, 121, 77, 49, 158, 173, 216, 222, 52, 246, 193, 45, 55, 138, 225, 90, 142, 152, 102, 93, 17, 232, 4, 94, 68, 20, 184, 183, 105, 84, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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