Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0abb22289b5597a430f0d89ecf7d28f789543621235f7f2b1f550057bcaae98d

Tx prefix hash: 1e3256e611944bdd71fb405c5c555e920d10e445649836d538b3d08a1fb439cd
Tx public key: 19fe4b8a423af708c4b2bdc167bfafb21e2bbd749132f9e949c36f1e804a1450
Timestamp: 1751026667 Timestamp [UCT]: 2025-06-27 12:17:47 Age [y:d:h:m:s]: 00:146:16:00:17
Block: 1313841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102856 RingCT/type: yes/0
Extra: 0119fe4b8a423af708c4b2bdc167bfafb21e2bbd749132f9e949c36f1e804a145002110000000bbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76bd216fc5ff114a61af7936cd36a47faa0a5dc7a2dd1f639781e29329a34dfb 0.600000000000 1801484 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": 1313851, "vin": [ { "gen": { "height": 1313841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76bd216fc5ff114a61af7936cd36a47faa0a5dc7a2dd1f639781e29329a34dfb" } } ], "extra": [ 1, 25, 254, 75, 138, 66, 58, 247, 8, 196, 178, 189, 193, 103, 191, 175, 178, 30, 43, 189, 116, 145, 50, 249, 233, 73, 195, 111, 30, 128, 74, 20, 80, 2, 17, 0, 0, 0, 11, 191, 81, 178, 162, 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