Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a31b12221ad39b3f8db22275fc90c66902d804aef40306d756ecdc55340fc217

Tx prefix hash: b2ec68b50d6db1059a3bcd0fe3f903af8f69e6f565125140afc3cb613a0683cf
Tx public key: 836793ebcfd0fc74e29e98ce9cd0daf4fb3a18513d0d97d776fa32257974b8f1
Timestamp: 1584922089 Timestamp [UCT]: 2020-03-23 00:08:09 Age [y:d:h:m:s]: 05:027:17:55:40
Block: 86871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177438 RingCT/type: yes/0
Extra: 01836793ebcfd0fc74e29e98ce9cd0daf4fb3a18513d0d97d776fa32257974b8f10211000000124ac5aa02000000000000000000

1 output(s) for total of 316.350547713000 dcy

stealth address amount amount idx
00: 1bfb63f6172dd318348ad93e2bd7d51025e89975af50d43f806a5a633d836620 316.350547713000 156699 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": 86881, "vin": [ { "gen": { "height": 86871 } } ], "vout": [ { "amount": 316350547713, "target": { "key": "1bfb63f6172dd318348ad93e2bd7d51025e89975af50d43f806a5a633d836620" } } ], "extra": [ 1, 131, 103, 147, 235, 207, 208, 252, 116, 226, 158, 152, 206, 156, 208, 218, 244, 251, 58, 24, 81, 61, 13, 151, 215, 118, 250, 50, 37, 121, 116, 184, 241, 2, 17, 0, 0, 0, 18, 74, 197, 170, 2, 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