Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01ea608bc4a3d95a737da42ad16e74fb0ab6ab1c5df545cbba91aa3cdb9a79ae

Tx prefix hash: 402d807e5d82776a5eab29d78efcff7b81c094d8bc28dbd5ec6385521bb4354e
Tx public key: 1f75e3fcb1f06a688c437dcf3fd4451fa69362c80323a2d8294712deff2210fa
Timestamp: 1736224430 Timestamp [UCT]: 2025-01-07 04:33:50 Age [y:d:h:m:s]: 00:298:17:27:32
Block: 1191922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210999 RingCT/type: yes/0
Extra: 011f75e3fcb1f06a688c437dcf3fd4451fa69362c80323a2d8294712deff2210fa021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98f18bdc7a66860482c2ba95870b7e00e709c7d5b9fbbf93220318938ec59dda 0.600000000000 1678465 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": 1191932, "vin": [ { "gen": { "height": 1191922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98f18bdc7a66860482c2ba95870b7e00e709c7d5b9fbbf93220318938ec59dda" } } ], "extra": [ 1, 31, 117, 227, 252, 177, 240, 106, 104, 140, 67, 125, 207, 63, 212, 69, 31, 166, 147, 98, 200, 3, 35, 162, 216, 41, 71, 18, 222, 255, 34, 16, 250, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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