Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c95bb24ff57448497622a6b1dbc4a442601dd632fda6f1b5b99b05f40c7c1b8f

Tx prefix hash: 021e0a07dd4b89fc21fd72a02073b6de62c74dbf63c17ac50f441a2f6ffedfa1
Tx public key: 08921585c73e4da446ee5e42caf27cb93b053a74b7284a5f70f20c7072afe865
Timestamp: 1745525765 Timestamp [UCT]: 2025-04-24 20:16:05 Age [y:d:h:m:s]: 00:210:10:19:33
Block: 1268665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148098 RingCT/type: yes/0
Extra: 0108921585c73e4da446ee5e42caf27cb93b053a74b7284a5f70f20c7072afe8650211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a641ada054ef3a452926745a7d22b3bd1d0aa1b2a5dc24cf6a7e0bce1043860c 0.600000000000 1755896 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": 1268675, "vin": [ { "gen": { "height": 1268665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a641ada054ef3a452926745a7d22b3bd1d0aa1b2a5dc24cf6a7e0bce1043860c" } } ], "extra": [ 1, 8, 146, 21, 133, 199, 62, 77, 164, 70, 238, 94, 66, 202, 242, 124, 185, 59, 5, 58, 116, 183, 40, 74, 95, 112, 242, 12, 112, 114, 175, 232, 101, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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