Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4ea27441ab4c4cf59cce974568f5e3c2c802996d23538e7fce2fcc53e924b41

Tx prefix hash: 642786a0e3ac1861e9e59ddcf2db6323cdf25968cdac98669ca4c9dab98ae498
Tx public key: eefd5074d4c2548429d76aade2f8a8bc0d5a585ef726ba9e391049a163bd60e3
Timestamp: 1763402931 Timestamp [UCT]: 2025-11-17 18:08:51 Age [y:d:h:m:s]: 00:050:16:29:52
Block: 1414257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36297 RingCT/type: yes/0
Extra: 01eefd5074d4c2548429d76aade2f8a8bc0d5a585ef726ba9e391049a163bd60e3021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c285b3671f5d6b51c86fda079b8f1ecaa76c015ad2146057d7e1a1664651408 0.600000000000 1902744 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": 1414267, "vin": [ { "gen": { "height": 1414257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c285b3671f5d6b51c86fda079b8f1ecaa76c015ad2146057d7e1a1664651408" } } ], "extra": [ 1, 238, 253, 80, 116, 212, 194, 84, 132, 41, 215, 106, 173, 226, 248, 168, 188, 13, 90, 88, 94, 247, 38, 186, 158, 57, 16, 73, 161, 99, 189, 96, 227, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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