Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9ccd1bde384f058eec625ac609f94adc375d3b7f757cdad0868ecdc647ed8ea

Tx prefix hash: 88606508bb11c5e6b71ae2c49b1633e2698737f41a10abd394abeeb9bcd2d3f1
Tx public key: 6914b80b516a0a9b107969f35d8be5033bf94e3c0d01c8c0011369f207e3d1c9
Timestamp: 1762986698 Timestamp [UCT]: 2025-11-12 22:31:38 Age [y:d:h:m:s]: 00:045:16:12:05
Block: 1410810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32705 RingCT/type: yes/0
Extra: 016914b80b516a0a9b107969f35d8be5033bf94e3c0d01c8c0011369f207e3d1c902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6517e3087123ed23451741d21bdaaa3c1f0044237f7ae9b69551bf3aec4a1d6 0.600000000000 1899265 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": 1410820, "vin": [ { "gen": { "height": 1410810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6517e3087123ed23451741d21bdaaa3c1f0044237f7ae9b69551bf3aec4a1d6" } } ], "extra": [ 1, 105, 20, 184, 11, 81, 106, 10, 155, 16, 121, 105, 243, 93, 139, 229, 3, 59, 249, 78, 60, 13, 1, 200, 192, 1, 19, 105, 242, 7, 227, 209, 201, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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