Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49b070688c6ac1183cbc71c61857aeb48647b661baab356ea354874f45db88de

Tx prefix hash: bf9ea8859416c48a0ef23d12d3575eb2d6a3ef6b7ec90987109e47d0e35ab30e
Tx public key: 14ad801ff7c6db60d2d5dfd09c1812b8973ec03e109c73b7d9ff167f8fd0fbcc
Timestamp: 1735581406 Timestamp [UCT]: 2024-12-30 17:56:46 Age [y:d:h:m:s]: 00:101:06:12:01
Block: 1186594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72167 RingCT/type: yes/0
Extra: 0114ad801ff7c6db60d2d5dfd09c1812b8973ec03e109c73b7d9ff167f8fd0fbcc021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69c644974de7481b5cf1db2b2bf6170cb41cec0896f402c296ad6c147a3cddd3 0.600000000000 1673077 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": 1186604, "vin": [ { "gen": { "height": 1186594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69c644974de7481b5cf1db2b2bf6170cb41cec0896f402c296ad6c147a3cddd3" } } ], "extra": [ 1, 20, 173, 128, 31, 247, 198, 219, 96, 210, 213, 223, 208, 156, 24, 18, 184, 151, 62, 192, 62, 16, 156, 115, 183, 217, 255, 22, 127, 143, 208, 251, 204, 2, 17, 0, 0, 0, 5, 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