Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d09e18716a2fb807ed4f1b34073cc0ae8a7e74ac095eea23f52973280f97c0

Tx prefix hash: 4c859000cc02aa3f21c3edba7fc4ea31ba7be06460898344bd88c9ad047ad3c6
Tx public key: 22fe478a0ea557330edeaf9ddc6ed9242ebfc08ea19b080e0991dc018b8b5ca6
Timestamp: 1582437187 Timestamp [UCT]: 2020-02-23 05:53:07 Age [y:d:h:m:s]: 05:252:16:04:25
Block: 70700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1331505 RingCT/type: yes/0
Extra: 0122fe478a0ea557330edeaf9ddc6ed9242ebfc08ea19b080e0991dc018b8b5ca6021100000002724f989b000000000000000000

1 output(s) for total of 357.890248479000 dcy

stealth address amount amount idx
00: 089d996ba41a5c72c9cae52a9e76210bbf10212860b92a724d6c8f07e403389a 357.890248479000 130616 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": 70710, "vin": [ { "gen": { "height": 70700 } } ], "vout": [ { "amount": 357890248479, "target": { "key": "089d996ba41a5c72c9cae52a9e76210bbf10212860b92a724d6c8f07e403389a" } } ], "extra": [ 1, 34, 254, 71, 138, 14, 165, 87, 51, 14, 222, 175, 157, 220, 110, 217, 36, 46, 191, 192, 142, 161, 155, 8, 14, 9, 145, 220, 1, 139, 139, 92, 166, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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