Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a600044c01d65bc31e4ab46749dd8f74dab4b70daa7ebd0c0b172fb6c74583f0

Tx prefix hash: 0abb1a1b8c5429fe8c82e9e8b3919e5a863289b0ae0255a364adb4532ff27b96
Tx public key: 6e7266b5dbbcc49ab64518546628d098ccef9a9dbb743a621d4634c5c15b3b05
Timestamp: 1734263872 Timestamp [UCT]: 2024-12-15 11:57:52 Age [y:d:h:m:s]: 00:102:13:19:06
Block: 1175722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73054 RingCT/type: yes/0
Extra: 016e7266b5dbbcc49ab64518546628d098ccef9a9dbb743a621d4634c5c15b3b050211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1744fd536efebccc89b8fd57791ad8667ee8f716cfa01cd54be5cc5e95df150 0.600000000000 1662043 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": 1175732, "vin": [ { "gen": { "height": 1175722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1744fd536efebccc89b8fd57791ad8667ee8f716cfa01cd54be5cc5e95df150" } } ], "extra": [ 1, 110, 114, 102, 181, 219, 188, 196, 154, 182, 69, 24, 84, 102, 40, 208, 152, 204, 239, 154, 157, 187, 116, 58, 98, 29, 70, 52, 197, 193, 91, 59, 5, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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