Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 339d063fb07e08b8e9b38db4c1a950ea6c3f56cb9bbf63303d71b432694d31b9

Tx prefix hash: 59c62465f7017e23b8fb4831e0f9a35037ce65a034801c82113ed0505ddbfbfd
Tx public key: 586a1856aad541ddcd5353e5ee7204abb2e13dcc47e13e84dc08d12fb875074d
Timestamp: 1703552272 Timestamp [UCT]: 2023-12-26 00:57:52 Age [y:d:h:m:s]: 01:151:20:28:41
Block: 921197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369678 RingCT/type: yes/0
Extra: 01586a1856aad541ddcd5353e5ee7204abb2e13dcc47e13e84dc08d12fb875074d021100000001ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a74cc3c83067639be8fa934f7a69e261f54f58aa54b9b846a4a243a0ae8ed742 0.600000000000 1378883 of 15

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": 921207, "vin": [ { "gen": { "height": 921197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a74cc3c83067639be8fa934f7a69e261f54f58aa54b9b846a4a243a0ae8ed742" } } ], "extra": [ 1, 88, 106, 24, 86, 170, 213, 65, 221, 205, 83, 83, 229, 238, 114, 4, 171, 178, 225, 61, 204, 71, 225, 62, 132, 220, 8, 209, 47, 184, 117, 7, 77, 2, 17, 0, 0, 0, 1, 173, 86, 148, 172, 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