Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353f7a51edf4f4d5e3c2a2499eb9fdd3b46179d97b55292f12c15957ffd73921

Tx prefix hash: 218ceb29c2e748db4fbfef8d5e7c37ef5b738d13e1eb4ca0dfa61d6132539801
Tx public key: e6b9a7e53fefb9da4f0da0fd44b0e91667bf3cf62e95b637693dda5d5f3ee5ab
Timestamp: 1658650861 Timestamp [UCT]: 2022-07-24 08:21:01 Age [y:d:h:m:s]: 02:295:21:51:56
Block: 550550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 732719 RingCT/type: yes/0
Extra: 01e6b9a7e53fefb9da4f0da0fd44b0e91667bf3cf62e95b637693dda5d5f3ee5ab0211000000056570b1ef000000000000000000

1 output(s) for total of 9.200245946000 dcy

stealth address amount amount idx
00: 2b5f0eec72d0a67af2a4193a043fefff9e14b52a346a12614f964d4ff739b519 9.200245946000 982045 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": 550560, "vin": [ { "gen": { "height": 550550 } } ], "vout": [ { "amount": 9200245946, "target": { "key": "2b5f0eec72d0a67af2a4193a043fefff9e14b52a346a12614f964d4ff739b519" } } ], "extra": [ 1, 230, 185, 167, 229, 63, 239, 185, 218, 79, 13, 160, 253, 68, 176, 233, 22, 103, 191, 60, 246, 46, 149, 182, 55, 105, 61, 218, 93, 95, 62, 229, 171, 2, 17, 0, 0, 0, 5, 101, 112, 177, 239, 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