Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02f0b5c0c90f3db40833591c448204c23483d6200ec8d314e9abde5ce266c1ef

Tx prefix hash: f59ab52193df60d2a61eb56d349fe81c5da9471212b499b67d73bffb512221d5
Tx public key: 8420cea9a4e0fc20fb33169395e9bbdc85dcdff9034077d9aee3d63827aa3a8d
Timestamp: 1712285306 Timestamp [UCT]: 2024-04-05 02:48:26 Age [y:d:h:m:s]: 01:021:00:22:17
Block: 993576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276002 RingCT/type: yes/0
Extra: 018420cea9a4e0fc20fb33169395e9bbdc85dcdff9034077d9aee3d63827aa3a8d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e1062b6ecc8c66b900e80bfaf446bf50d7ab253d63b78eed192dd2774caa752 0.600000000000 1453962 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": 993586, "vin": [ { "gen": { "height": 993576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e1062b6ecc8c66b900e80bfaf446bf50d7ab253d63b78eed192dd2774caa752" } } ], "extra": [ 1, 132, 32, 206, 169, 164, 224, 252, 32, 251, 51, 22, 147, 149, 233, 187, 220, 133, 220, 223, 249, 3, 64, 119, 217, 174, 227, 214, 56, 39, 170, 58, 141, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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