Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f7a0ba59d6808b1c8f9854cb1edeff5fb0b7d678f48679b5114ec6c119b0f91

Tx prefix hash: 43015d2a9d4e8d9e45c33dfdb54d56daa99e177868b2866cd7600d9794b0f99d
Tx public key: 5f9e329c04d5858da6bb17a07406cadb07932966aba3b54afbd74d50c3661296
Timestamp: 1617486119 Timestamp [UCT]: 2021-04-03 21:41:59 Age [y:d:h:m:s]: 03:306:14:14:25
Block: 232666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 978521 RingCT/type: yes/0
Extra: 015f9e329c04d5858da6bb17a07406cadb07932966aba3b54afbd74d50c3661296021100000013ece3035d000000000000000000

1 output(s) for total of 104.011542116000 dcy

stealth address amount amount idx
00: 13fdeab4caf69e1731f6013c9bc8f84436e8ce3d7b17d241efabe3716060a78f 104.011542116000 483372 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": 232676, "vin": [ { "gen": { "height": 232666 } } ], "vout": [ { "amount": 104011542116, "target": { "key": "13fdeab4caf69e1731f6013c9bc8f84436e8ce3d7b17d241efabe3716060a78f" } } ], "extra": [ 1, 95, 158, 50, 156, 4, 213, 133, 141, 166, 187, 23, 160, 116, 6, 202, 219, 7, 147, 41, 102, 171, 163, 181, 74, 251, 215, 77, 80, 195, 102, 18, 150, 2, 17, 0, 0, 0, 19, 236, 227, 3, 93, 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