Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abfd333c44a33cde9ce9ab185f04ac8dd68e60b59e6776c0beed7d3af5ccc7ed

Tx prefix hash: a4c1dc8d70c907a437c2b4086c5dcd225b7caac03ab674ce622729069082b5be
Tx public key: ba9e3b38dd7e5754a57f433e479c8d0b906050ec56e90c8c03fc5c323aaaa159
Timestamp: 1731210472 Timestamp [UCT]: 2024-11-10 03:47:52 Age [y:d:h:m:s]: 00:130:13:31:53
Block: 1150415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93146 RingCT/type: yes/0
Extra: 01ba9e3b38dd7e5754a57f433e479c8d0b906050ec56e90c8c03fc5c323aaaa159021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa29a2a18a1a0709d668bd730fb5e8b6852cd88f8f44c5813aaddf16e41d3a50 0.600000000000 1635720 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": 1150425, "vin": [ { "gen": { "height": 1150415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa29a2a18a1a0709d668bd730fb5e8b6852cd88f8f44c5813aaddf16e41d3a50" } } ], "extra": [ 1, 186, 158, 59, 56, 221, 126, 87, 84, 165, 127, 67, 62, 71, 156, 141, 11, 144, 96, 80, 236, 86, 233, 12, 140, 3, 252, 92, 50, 58, 170, 161, 89, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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