Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5c2edaed62fb2712831b3eeff187f87bf1e575a12c0e102297e503e64d0ca9c

Tx prefix hash: c0bc07e39021edb0ae7b04665a9d21ac21642041cb6571c29ad38a224973be47
Tx public key: b21a5fccc2f7ce16446da627c0eee3e8d7abf51fda8ee4793faaf79e29a95fa7
Timestamp: 1581090712 Timestamp [UCT]: 2020-02-07 15:51:52 Age [y:d:h:m:s]: 04:334:16:55:51
Block: 60672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130677 RingCT/type: yes/0
Extra: 01b21a5fccc2f7ce16446da627c0eee3e8d7abf51fda8ee4793faaf79e29a95fa702110000000303d36d11000000000000000000

1 output(s) for total of 386.339661715000 dcy

stealth address amount amount idx
00: 6107a9cc340bcac658c332fe70ea36c8267588d6a4a8201e24de478e951f8611 386.339661715000 111712 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": 60682, "vin": [ { "gen": { "height": 60672 } } ], "vout": [ { "amount": 386339661715, "target": { "key": "6107a9cc340bcac658c332fe70ea36c8267588d6a4a8201e24de478e951f8611" } } ], "extra": [ 1, 178, 26, 95, 204, 194, 247, 206, 22, 68, 109, 166, 39, 192, 238, 227, 232, 215, 171, 245, 31, 218, 142, 228, 121, 63, 170, 247, 158, 41, 169, 95, 167, 2, 17, 0, 0, 0, 3, 3, 211, 109, 17, 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