Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4201496c27c997330aadb6443235e076c60ae9c10c05823c4e03317594baaeb6

Tx prefix hash: bd21103e396584956e5db9f947fc1fde75ffdd780a4469d8913cc62e3a516aa8
Tx public key: a2acc02e2df3cd750b4f54ef40f0ad6cfa4b25d71eef9184178a058551339422
Timestamp: 1725094408 Timestamp [UCT]: 2024-08-31 08:53:28 Age [y:d:h:m:s]: 00:249:13:08:25
Block: 1099792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178219 RingCT/type: yes/0
Extra: 01a2acc02e2df3cd750b4f54ef40f0ad6cfa4b25d71eef9184178a058551339422021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f63ab416f5ad11bf8664eafb7d6733b7dd5fd8645a658a3a2f484ae0b2d3b44 0.600000000000 1575761 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": 1099802, "vin": [ { "gen": { "height": 1099792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f63ab416f5ad11bf8664eafb7d6733b7dd5fd8645a658a3a2f484ae0b2d3b44" } } ], "extra": [ 1, 162, 172, 192, 46, 45, 243, 205, 117, 11, 79, 84, 239, 64, 240, 173, 108, 250, 75, 37, 215, 30, 239, 145, 132, 23, 138, 5, 133, 81, 51, 148, 34, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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