Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 061650bc0cf08adcea7ccadeb327e7a7c29ebc2e44010232ebdfed30a994c57a

Tx prefix hash: b2595dcf72bfb2fedc5149fa8864cac9df274f0f4eacb42f26184c975e58657e
Tx public key: 649d7294aa9c8ea80f4e223ac147fc59c11b7738cc304a9c26c6986eb666234c
Timestamp: 1711688759 Timestamp [UCT]: 2024-03-29 05:05:59 Age [y:d:h:m:s]: 01:045:07:25:40
Block: 988664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293356 RingCT/type: yes/0
Extra: 01649d7294aa9c8ea80f4e223ac147fc59c11b7738cc304a9c26c6986eb666234c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae867a7135feeb39ceacb6cc36cd1c24d5506e475f6ec0f8c4de83b401f5e73e 0.600000000000 1448945 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": 988674, "vin": [ { "gen": { "height": 988664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae867a7135feeb39ceacb6cc36cd1c24d5506e475f6ec0f8c4de83b401f5e73e" } } ], "extra": [ 1, 100, 157, 114, 148, 170, 156, 142, 168, 15, 78, 34, 58, 193, 71, 252, 89, 193, 27, 119, 56, 204, 48, 74, 156, 38, 198, 152, 110, 182, 102, 35, 76, 2, 17, 0, 0, 0, 3, 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