Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b88c4050bb5246f4a9119e3545538d665a41b2f8b3a4842fdd375cb7fa279659

Tx prefix hash: 2691dc9f45aff3385aa00bab3a1659be7245e8929f22495b4ba8eb99cebfa021
Tx public key: d4bb7fdce775263d2a4e94cc1a7b04e298901e647cd8b8b2c6d9489e24702cc9
Timestamp: 1754570542 Timestamp [UCT]: 2025-08-07 12:42:22 Age [y:d:h:m:s]: 00:105:10:39:50
Block: 1342136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74420 RingCT/type: yes/0
Extra: 01d4bb7fdce775263d2a4e94cc1a7b04e298901e647cd8b8b2c6d9489e24702cc902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fb0f76cf81e8419f291e9c6f2ecb69d2a5d2340dbd03c6e1c591059a4004176 0.600000000000 1829965 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": 1342146, "vin": [ { "gen": { "height": 1342136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fb0f76cf81e8419f291e9c6f2ecb69d2a5d2340dbd03c6e1c591059a4004176" } } ], "extra": [ 1, 212, 187, 127, 220, 231, 117, 38, 61, 42, 78, 148, 204, 26, 123, 4, 226, 152, 144, 30, 100, 124, 216, 184, 178, 198, 217, 72, 158, 36, 112, 44, 201, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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