Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd37744f26f4f7848695118489ae387a5eba028a9b78356b7922be4a37de59e1

Tx prefix hash: 5024b8c3a534a1b9d8109bf1fffbf3e822146eebe9ea4c2436646e25eacfca9c
Tx public key: af1bfb23384dd56d2cc0d56816fb80f8dc6f94b3f0c350957596e801f2d783e7
Timestamp: 1577093236 Timestamp [UCT]: 2019-12-23 09:27:16 Age [y:d:h:m:s]: 05:007:04:52:54
Block: 29914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155143 RingCT/type: yes/0
Extra: 01af1bfb23384dd56d2cc0d56816fb80f8dc6f94b3f0c350957596e801f2d783e702110000000ed81c26c0000000000000000000

1 output(s) for total of 488.521140711000 dcy

stealth address amount amount idx
00: d496aaddd7dba2491d55da75b5ed5f5969552a9bb042d5eff4a420854e742964 488.521140711000 49352 of 0

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": 29924, "vin": [ { "gen": { "height": 29914 } } ], "vout": [ { "amount": 488521140711, "target": { "key": "d496aaddd7dba2491d55da75b5ed5f5969552a9bb042d5eff4a420854e742964" } } ], "extra": [ 1, 175, 27, 251, 35, 56, 77, 213, 109, 44, 192, 213, 104, 22, 251, 128, 248, 220, 111, 148, 179, 240, 195, 80, 149, 117, 150, 232, 1, 242, 215, 131, 231, 2, 17, 0, 0, 0, 14, 216, 28, 38, 192, 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