Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42717f749d0c132e3fd43664681714a4769b4c46fd4bcff89bc9338a4d6d8931

Tx prefix hash: 8232623e815cc3f6af853864ce7f70c8469ea87e716dd45581f8181e46f1ae09
Tx public key: a3ea16b23b2b82d03e38660e202cc335a0286dd8581f6095bf56f7b5f7eee321
Timestamp: 1724827541 Timestamp [UCT]: 2024-08-28 06:45:41 Age [y:d:h:m:s]: 00:289:02:53:09
Block: 1097577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206478 RingCT/type: yes/0
Extra: 01a3ea16b23b2b82d03e38660e202cc335a0286dd8581f6095bf56f7b5f7eee32102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131476500f54387a9297f5a2dd2d33c7a5a379adaf3125957473c9b5bb5dbc46 0.600000000000 1572984 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": 1097587, "vin": [ { "gen": { "height": 1097577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131476500f54387a9297f5a2dd2d33c7a5a379adaf3125957473c9b5bb5dbc46" } } ], "extra": [ 1, 163, 234, 22, 178, 59, 43, 130, 208, 62, 56, 102, 14, 32, 44, 195, 53, 160, 40, 109, 216, 88, 31, 96, 149, 191, 86, 247, 181, 247, 238, 227, 33, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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