Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fdf149b7a610cfad356198f4dcbf7972baedbddcac998ff14e046c444acb9be

Tx prefix hash: c523517f2bb011e38ecb7f53e804f37f009cc5b1596f40a96a7e36c209dd604d
Tx public key: e596f3fcfbba41d24acb239a51d97fc92c671d73bb28a4a9d250ba48aac28a95
Timestamp: 1748930297 Timestamp [UCT]: 2025-06-03 05:58:17 Age [y:d:h:m:s]: 00:164:18:58:26
Block: 1296862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115455 RingCT/type: yes/0
Extra: 01e596f3fcfbba41d24acb239a51d97fc92c671d73bb28a4a9d250ba48aac28a95021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f5828ac049ba36a661b4f8e976bb3c14004ea89810a8cad9b6476bc3bb1fc51 0.600000000000 1784379 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": 1296872, "vin": [ { "gen": { "height": 1296862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f5828ac049ba36a661b4f8e976bb3c14004ea89810a8cad9b6476bc3bb1fc51" } } ], "extra": [ 1, 229, 150, 243, 252, 251, 186, 65, 210, 74, 203, 35, 154, 81, 217, 127, 201, 44, 103, 29, 115, 187, 40, 164, 169, 210, 80, 186, 72, 170, 194, 138, 149, 2, 17, 0, 0, 0, 5, 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