Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9d72f269b510bea38cabf83af863cd9a12c6cae919d015c66aafcbc1777763f

Tx prefix hash: 3d7afaf07134cc5cce816f012aaaa4dfd156f71ebb01d42d0a658df4c7d40e9b
Tx public key: 840e6a2a4d3c16af6b0722e8e126356550fc25873dad144880ae4c95250d6fed
Timestamp: 1706795547 Timestamp [UCT]: 2024-02-01 13:52:27 Age [y:d:h:m:s]: 01:279:10:25:48
Block: 948059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458498 RingCT/type: yes/0
Extra: 01840e6a2a4d3c16af6b0722e8e126356550fc25873dad144880ae4c95250d6fed02110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12352160beba5669a70405d8c4d4280b87d8c8b0f6f811bc4de2690e48309aa8 0.600000000000 1406431 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": 948069, "vin": [ { "gen": { "height": 948059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12352160beba5669a70405d8c4d4280b87d8c8b0f6f811bc4de2690e48309aa8" } } ], "extra": [ 1, 132, 14, 106, 42, 77, 60, 22, 175, 107, 7, 34, 232, 225, 38, 53, 101, 80, 252, 37, 135, 61, 173, 20, 72, 128, 174, 76, 149, 37, 13, 111, 237, 2, 17, 0, 0, 0, 13, 82, 212, 126, 148, 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