Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc59c9a59c718ee8f6ca4595e54dd269853f06177948b479e447a750d0b8aed7

Tx prefix hash: 2b35428d5f5483df7910b88e250d7fce845eedeb231040d15d11aa72264f8e46
Tx public key: 0770199cb697cb39c4380e58c6a11c1ad05d50156b8fa4b958f3b60fbefebfa1
Timestamp: 1737442517 Timestamp [UCT]: 2025-01-21 06:55:17 Age [y:d:h:m:s]: 00:329:22:45:12
Block: 1201969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233394 RingCT/type: yes/0
Extra: 010770199cb697cb39c4380e58c6a11c1ad05d50156b8fa4b958f3b60fbefebfa1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d38386fc935f1b735ce0bb23d8eec44b1e6fe325877b8f228ba7a3afc038625 0.600000000000 1688628 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": 1201979, "vin": [ { "gen": { "height": 1201969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d38386fc935f1b735ce0bb23d8eec44b1e6fe325877b8f228ba7a3afc038625" } } ], "extra": [ 1, 7, 112, 25, 156, 182, 151, 203, 57, 196, 56, 14, 88, 198, 161, 28, 26, 208, 93, 80, 21, 107, 143, 164, 185, 88, 243, 182, 15, 190, 254, 191, 161, 2, 17, 0, 0, 0, 1, 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