Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfb6a33dfd0f8df0887251ca7b230044ca1440eedcdaeb391cea231c93c9fd40

Tx prefix hash: 7a5c715b3c89b0a84635a9831a82b324eb5291f97cf5811e813394f944555a30
Tx public key: 42ded2645e86781a9d75ff713a06be7df07131535935ab3dc4c5f2306ec9fbb8
Timestamp: 1708146599 Timestamp [UCT]: 2024-02-17 05:09:59 Age [y:d:h:m:s]: 01:028:18:27:00
Block: 959280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281603 RingCT/type: yes/0
Extra: 0142ded2645e86781a9d75ff713a06be7df07131535935ab3dc4c5f2306ec9fbb802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8e3c21b1b477bbf61c7625dde7c717f79f943674e4ac46ce584cf42fa8cf5c6 0.600000000000 1418811 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": 959290, "vin": [ { "gen": { "height": 959280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8e3c21b1b477bbf61c7625dde7c717f79f943674e4ac46ce584cf42fa8cf5c6" } } ], "extra": [ 1, 66, 222, 210, 100, 94, 134, 120, 26, 157, 117, 255, 113, 58, 6, 190, 125, 240, 113, 49, 83, 89, 53, 171, 61, 196, 197, 242, 48, 110, 201, 251, 184, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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