Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70f10a511957f68d39e20e4e7084130a4248704b3205904d079ca44e998fd069

Tx prefix hash: fb14c73c4d2575673966354b1fe5602bb161e36498caa56f79e7b3b9a0e109c5
Tx public key: 1035942ac7f79d880735e5ef1fe57c73451fd1211bd510c8b0ec9aa7b9c3f1bb
Timestamp: 1731268048 Timestamp [UCT]: 2024-11-10 19:47:28 Age [y:d:h:m:s]: 00:364:08:18:38
Block: 1150893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257936 RingCT/type: yes/0
Extra: 011035942ac7f79d880735e5ef1fe57c73451fd1211bd510c8b0ec9aa7b9c3f1bb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6b3073259aa7d2aefd25d82e41563be37e45063e30726a4ffe87a01c7456a74 0.600000000000 1636320 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": 1150903, "vin": [ { "gen": { "height": 1150893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6b3073259aa7d2aefd25d82e41563be37e45063e30726a4ffe87a01c7456a74" } } ], "extra": [ 1, 16, 53, 148, 42, 199, 247, 157, 136, 7, 53, 229, 239, 31, 229, 124, 115, 69, 31, 209, 33, 27, 213, 16, 200, 176, 236, 154, 167, 185, 195, 241, 187, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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