Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7a81d6fe6dda86fcb10a1889405f51a3fdbd7ca7b4b16a52505d0f9a62bf014

Tx prefix hash: 043c1dbff596b5dcc5adb6f7e69c1944f9b320548fb80e18d7cf66cbbf5b8d30
Tx public key: a42734a4d2e31fbe50f6626eb6ff0f0c597a02cf59ecfd644d9f8beee5ca7756
Timestamp: 1746002405 Timestamp [UCT]: 2025-04-30 08:40:05 Age [y:d:h:m:s]: 00:252:03:25:39
Block: 1272632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177974 RingCT/type: yes/0
Extra: 01a42734a4d2e31fbe50f6626eb6ff0f0c597a02cf59ecfd644d9f8beee5ca77560211000000062609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fab0ccf90eec169dc318c49fffd6f71c2daf3c598ebca8604c51d6f1b4a4f078 0.600000000000 1759907 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": 1272642, "vin": [ { "gen": { "height": 1272632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fab0ccf90eec169dc318c49fffd6f71c2daf3c598ebca8604c51d6f1b4a4f078" } } ], "extra": [ 1, 164, 39, 52, 164, 210, 227, 31, 190, 80, 246, 98, 110, 182, 255, 15, 12, 89, 122, 2, 207, 89, 236, 253, 100, 77, 159, 139, 238, 229, 202, 119, 86, 2, 17, 0, 0, 0, 6, 38, 9, 179, 160, 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