Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da72897a3f70f0f8083a79231d2dd2b2c01cc9bd0142dffaf84cd504cf1aec1c

Tx prefix hash: a17b164d6467d73426d0a9feff63d36cd1cd1a9e6fbda3db376355f4e93e3b11
Tx public key: 6ab50bff25f37beb221988ea462b07e832b5bc1c0db1427c788ebbf7f348d946
Timestamp: 1577242694 Timestamp [UCT]: 2019-12-25 02:58:14 Age [y:d:h:m:s]: 05:048:22:54:06
Block: 31134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184763 RingCT/type: yes/0
Extra: 016ab50bff25f37beb221988ea462b07e832b5bc1c0db1427c788ebbf7f348d9460211000000028a2ee0d9000000000000000000

1 output(s) for total of 483.995132816000 dcy

stealth address amount amount idx
00: 5be094a1881953eac35c0e1a3c5f224a5a88b050eaa1f3e00dd5c2a9d64e4a35 483.995132816000 51464 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": 31144, "vin": [ { "gen": { "height": 31134 } } ], "vout": [ { "amount": 483995132816, "target": { "key": "5be094a1881953eac35c0e1a3c5f224a5a88b050eaa1f3e00dd5c2a9d64e4a35" } } ], "extra": [ 1, 106, 181, 11, 255, 37, 243, 123, 235, 34, 25, 136, 234, 70, 43, 7, 232, 50, 181, 188, 28, 13, 177, 66, 124, 120, 142, 187, 247, 243, 72, 217, 70, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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