Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 614e010b587594c382bdcfbc8e6fe2a8f8ee56fbeb1d4be7156caa8446eb64dc

Tx prefix hash: 9eae194eae6d926139e1203823b6ea702ba284298575b7f44b74ded59b83e246
Tx public key: 4a969b4b5f8b9b2b70e1eb54723f24776c0374fb47de4d65977af8739f5a983e
Timestamp: 1637395121 Timestamp [UCT]: 2021-11-20 07:58:41 Age [y:d:h:m:s]: 03:349:16:41:40
Block: 378160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1026267 RingCT/type: yes/0
Extra: 014a969b4b5f8b9b2b70e1eb54723f24776c0374fb47de4d65977af8739f5a983e02110000003cd6e4826b000000000000000000

1 output(s) for total of 34.276725123000 dcy

stealth address amount amount idx
00: d87effaf7f18d4ffe32e2bcf184e62b2502eb7aa30f24a733da2e127663e2d17 34.276725123000 764769 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": 378170, "vin": [ { "gen": { "height": 378160 } } ], "vout": [ { "amount": 34276725123, "target": { "key": "d87effaf7f18d4ffe32e2bcf184e62b2502eb7aa30f24a733da2e127663e2d17" } } ], "extra": [ 1, 74, 150, 155, 75, 95, 139, 155, 43, 112, 225, 235, 84, 114, 63, 36, 119, 108, 3, 116, 251, 71, 222, 77, 101, 151, 122, 248, 115, 159, 90, 152, 62, 2, 17, 0, 0, 0, 60, 214, 228, 130, 107, 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