Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff3defe44a7afcccdfd967d1c63658278f7a53cc4be45d9c511aa73a36b99e7a

Tx prefix hash: 0357130bbfc057971d0ba52feefdda6d4d574ad695b0ed4f6fae35b760dc4b6a
Tx public key: 2a0badc8f062a34fee97cac1dd68106cbb65546d4a89d574fd055ba7e193f2fc
Timestamp: 1728178707 Timestamp [UCT]: 2024-10-06 01:38:27 Age [y:d:h:m:s]: 00:176:09:07:10
Block: 1125362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125844 RingCT/type: yes/0
Extra: 012a0badc8f062a34fee97cac1dd68106cbb65546d4a89d574fd055ba7e193f2fc02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37860eb754cbcedca9a8258caa9f4fa65e5b5bac0b3b2294ad82ccf931dd0204 0.600000000000 1608043 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": 1125372, "vin": [ { "gen": { "height": 1125362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37860eb754cbcedca9a8258caa9f4fa65e5b5bac0b3b2294ad82ccf931dd0204" } } ], "extra": [ 1, 42, 11, 173, 200, 240, 98, 163, 79, 238, 151, 202, 193, 221, 104, 16, 108, 187, 101, 84, 109, 74, 137, 213, 116, 253, 5, 91, 167, 225, 147, 242, 252, 2, 17, 0, 0, 0, 6, 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