Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fce6d3245d5709a71624c267ab52e5e5bc0ceadda7c13956c03878b40e362f6

Tx prefix hash: de1fbc977aac8baaf3dde85c50a33419ba9af2cdefa4198eaa941c5c5886b74f
Tx public key: e654f4e16030b1066c1f53bb9e12304b71fa8c88910394f43e0d22b0bdc27045
Timestamp: 1762483756 Timestamp [UCT]: 2025-11-07 02:49:16 Age [y:d:h:m:s]: 00:046:13:23:55
Block: 1406635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33328 RingCT/type: yes/0
Extra: 01e654f4e16030b1066c1f53bb9e12304b71fa8c88910394f43e0d22b0bdc27045021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18f3835cacbb70e7d1f4948cfe12a6b9b3ea9867dcad03db233ad4a1c8b8e347 0.600000000000 1895022 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": 1406645, "vin": [ { "gen": { "height": 1406635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18f3835cacbb70e7d1f4948cfe12a6b9b3ea9867dcad03db233ad4a1c8b8e347" } } ], "extra": [ 1, 230, 84, 244, 225, 96, 48, 177, 6, 108, 31, 83, 187, 158, 18, 48, 75, 113, 250, 140, 136, 145, 3, 148, 244, 62, 13, 34, 176, 189, 194, 112, 69, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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