Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cbe79b3b022ebb190bf0f5803965aaf7e8a75991828edbdaaff635cf09e5b64

Tx prefix hash: 21eed21dee6b28fd54b6df505f529aa557a1d722c5e2c29b4e8c5ce0ea604960
Tx public key: dbeeef2fa28388627e3e7a6c1cec7c76eaf874537cb189cdb1a5d7e238c67cf7
Timestamp: 1740187201 Timestamp [UCT]: 2025-02-22 01:20:01 Age [y:d:h:m:s]: 00:228:06:30:01
Block: 1224442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160862 RingCT/type: yes/0
Extra: 01dbeeef2fa28388627e3e7a6c1cec7c76eaf874537cb189cdb1a5d7e238c67cf7021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53762b2c4eb83c7de864e1de7fd1494661590fb4c7d9c3b85bc8b8228c6d37cb 0.600000000000 1711305 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": 1224452, "vin": [ { "gen": { "height": 1224442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53762b2c4eb83c7de864e1de7fd1494661590fb4c7d9c3b85bc8b8228c6d37cb" } } ], "extra": [ 1, 219, 238, 239, 47, 162, 131, 136, 98, 126, 62, 122, 108, 28, 236, 124, 118, 234, 248, 116, 83, 124, 177, 137, 205, 177, 165, 215, 226, 56, 198, 124, 247, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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