Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2800ea225e74ff6b4eab5b5a3e7e291ab2a0842943c1b46fb2194d7fd9086017

Tx prefix hash: 5c9047453ea8687645e2fd495d927408d4855375f4c2babd186ba373d91246dd
Tx public key: 522fbda1e0759bdae9c786cb7de2160c5b3a037cf0c0c0be1fb73cd972c638af
Timestamp: 1761489224 Timestamp [UCT]: 2025-10-26 14:33:44 Age [y:d:h:m:s]: 00:031:19:45:43
Block: 1398411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22778 RingCT/type: yes/0
Extra: 01522fbda1e0759bdae9c786cb7de2160c5b3a037cf0c0c0be1fb73cd972c638af021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de3709da5b501547e2cc40dc4c9a3cd7e88264479a098fb553072346d3ff85bb 0.600000000000 1886710 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": 1398421, "vin": [ { "gen": { "height": 1398411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de3709da5b501547e2cc40dc4c9a3cd7e88264479a098fb553072346d3ff85bb" } } ], "extra": [ 1, 82, 47, 189, 161, 224, 117, 155, 218, 233, 199, 134, 203, 125, 226, 22, 12, 91, 58, 3, 124, 240, 192, 192, 190, 31, 183, 60, 217, 114, 198, 56, 175, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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