Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcbdd6abbbe3aefd69db8668e189e3bf03c50d96e925fb43fb617f68f08825d9

Tx prefix hash: 2689c33e4ee7b90d27142712f1a7e68f4fa62da15098d070be659a2d6bad8d59
Tx public key: c03f4058536ef2f53aea97027ef16e0cd97c15f1c55f40b698756252545cdd43
Timestamp: 1719255492 Timestamp [UCT]: 2024-06-24 18:58:12 Age [y:d:h:m:s]: 00:324:14:38:12
Block: 1051368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231998 RingCT/type: yes/0
Extra: 01c03f4058536ef2f53aea97027ef16e0cd97c15f1c55f40b698756252545cdd4302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ef08fc7e18d72f2209e5aa9c2abfd7f7ecd8588bc025bfa159258c7c9a8342c 0.600000000000 1521679 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": 1051378, "vin": [ { "gen": { "height": 1051368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ef08fc7e18d72f2209e5aa9c2abfd7f7ecd8588bc025bfa159258c7c9a8342c" } } ], "extra": [ 1, 192, 63, 64, 88, 83, 110, 242, 245, 58, 234, 151, 2, 126, 241, 110, 12, 217, 124, 21, 241, 197, 95, 64, 182, 152, 117, 98, 82, 84, 92, 221, 67, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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