Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b0166be14714ce790659c4ffb0e22f3f38842f1dfc4ffafd67572a118495044

Tx prefix hash: 47c4edd3d5b287f50e12feb9b35992d278729295cd3e86c2c8e02955efe31f8c
Tx public key: e8f5b725c2984a0ab4858b3a94e823fecc94ec8442b600f59ad69ea5f9d3d433
Timestamp: 1634948507 Timestamp [UCT]: 2021-10-23 00:21:47 Age [y:d:h:m:s]: 03:114:02:01:28
Block: 358459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 859614 RingCT/type: yes/0
Extra: 01e8f5b725c2984a0ab4858b3a94e823fecc94ec8442b600f59ad69ea5f9d3d4330211000000085410958b000000000000000000

1 output(s) for total of 39.836111639000 dcy

stealth address amount amount idx
00: 473b3feb50ff69cc7447c6e00472392b7becbea007b3f7bbc450df6ee36fa74a 39.836111639000 730388 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": 358469, "vin": [ { "gen": { "height": 358459 } } ], "vout": [ { "amount": 39836111639, "target": { "key": "473b3feb50ff69cc7447c6e00472392b7becbea007b3f7bbc450df6ee36fa74a" } } ], "extra": [ 1, 232, 245, 183, 37, 194, 152, 74, 10, 180, 133, 139, 58, 148, 232, 35, 254, 204, 148, 236, 132, 66, 182, 0, 245, 154, 214, 158, 165, 249, 211, 212, 51, 2, 17, 0, 0, 0, 8, 84, 16, 149, 139, 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