Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b307de46839fdaa0d4121b3ef6cbc240744d5fe74f7a5cdb3996cbb631a43094

Tx prefix hash: 0c478b8faa6852aeec456f60f8548dfc056033314134a04dd02b36ce777d68c2
Tx public key: 8547b69989b43703aaf8e048ffb2f363a50ce430a425bad6d1c3ab3882e52e1a
Timestamp: 1724138214 Timestamp [UCT]: 2024-08-20 07:16:54 Age [y:d:h:m:s]: 00:252:13:25:38
Block: 1091874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180387 RingCT/type: yes/0
Extra: 018547b69989b43703aaf8e048ffb2f363a50ce430a425bad6d1c3ab3882e52e1a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53e2f72255152f6f6d6c97ea73d33d5fc4bf4e8b8dc76d0339b78c66d17b8881 0.600000000000 1566509 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": 1091884, "vin": [ { "gen": { "height": 1091874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53e2f72255152f6f6d6c97ea73d33d5fc4bf4e8b8dc76d0339b78c66d17b8881" } } ], "extra": [ 1, 133, 71, 182, 153, 137, 180, 55, 3, 170, 248, 224, 72, 255, 178, 243, 99, 165, 12, 228, 48, 164, 37, 186, 214, 209, 195, 171, 56, 130, 229, 46, 26, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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