Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 386a5bf12634c838f4eeaaf5429e4c65a5a96b34287a40c492b21a38fbe9a4c6

Tx prefix hash: 7e6ee99d5b0f5fff75cbe6e02ffa8e78602e81f0505581ffe3e669a7f917aa5a
Tx public key: 2457ad783d3924b922d292d07c9e7ee62313433c89927c2b683a07defbe2e325
Timestamp: 1708828348 Timestamp [UCT]: 2024-02-25 02:32:28 Age [y:d:h:m:s]: 01:042:06:54:24
Block: 964941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291231 RingCT/type: yes/0
Extra: 012457ad783d3924b922d292d07c9e7ee62313433c89927c2b683a07defbe2e32502110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 956d5aa418b4568fcc7b36019f63d6c9499befb24ba744e40f67664406da9870 0.600000000000 1424684 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": 964951, "vin": [ { "gen": { "height": 964941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "956d5aa418b4568fcc7b36019f63d6c9499befb24ba744e40f67664406da9870" } } ], "extra": [ 1, 36, 87, 173, 120, 61, 57, 36, 185, 34, 210, 146, 208, 124, 158, 126, 230, 35, 19, 67, 60, 137, 146, 124, 43, 104, 58, 7, 222, 251, 226, 227, 37, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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