Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b417d7f761f5818827d59ba1587ba3b0130fb06e4e1890170cdf916017ea4f3

Tx prefix hash: 3174b0c6ef7728f8d05525bf4b5ee42ad6e7d038f797d47a27dbfb674176f631
Tx public key: 3ddf1af9666570dde5e6123d1eef52eeeceff290e275633bcf7d45c9c1afe7f7
Timestamp: 1710552458 Timestamp [UCT]: 2024-03-16 01:27:38 Age [y:d:h:m:s]: 01:062:03:46:16
Block: 979245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305419 RingCT/type: yes/0
Extra: 013ddf1af9666570dde5e6123d1eef52eeeceff290e275633bcf7d45c9c1afe7f702110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c24c4c97f006c9854cd0a3cff007cb08ffa0721b6c1b9269c6d88fd12e21d50 0.600000000000 1439278 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": 979255, "vin": [ { "gen": { "height": 979245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c24c4c97f006c9854cd0a3cff007cb08ffa0721b6c1b9269c6d88fd12e21d50" } } ], "extra": [ 1, 61, 223, 26, 249, 102, 101, 112, 221, 229, 230, 18, 61, 30, 239, 82, 238, 236, 239, 242, 144, 226, 117, 99, 59, 207, 125, 69, 201, 193, 175, 231, 247, 2, 17, 0, 0, 0, 6, 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