Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f01aedd51781425677c3b6b341d3120b4bc1fef4e117e63b63871e505fe94c3c

Tx prefix hash: 3f4ff4b2ab61556cdf8e8bce5bc2bdf18d5a29cac8d9af00405f64bb0939af91
Tx public key: 34ec834c6f17056362a70182bc9c009cc5e9998e17d98f087e12312f4d5a5c81
Timestamp: 1725784811 Timestamp [UCT]: 2024-09-08 08:40:11 Age [y:d:h:m:s]: 00:122:20:00:05
Block: 1105511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87845 RingCT/type: yes/0
Extra: 0134ec834c6f17056362a70182bc9c009cc5e9998e17d98f087e12312f4d5a5c81021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e782325002e1e9800bc744b662f1d382657d6f36d9bb4c2c97a05eef7dd07ce4 0.600000000000 1582866 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": 1105521, "vin": [ { "gen": { "height": 1105511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e782325002e1e9800bc744b662f1d382657d6f36d9bb4c2c97a05eef7dd07ce4" } } ], "extra": [ 1, 52, 236, 131, 76, 111, 23, 5, 99, 98, 167, 1, 130, 188, 156, 0, 156, 197, 233, 153, 142, 23, 217, 143, 8, 126, 18, 49, 47, 77, 90, 92, 129, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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