Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 997a387c925d9ed30447bcf8e19ceaff2d24db83c20e63875386a0eef4b9a00a

Tx prefix hash: 639da0c1f4fc4b315f180927899026e84e2f8e924e7856c2283083cfc6ce0771
Tx public key: 550dd1d49254b0aea024d36ff3ebdd65a5a63621f49c1c7fc869a80f57d86160
Timestamp: 1726885596 Timestamp [UCT]: 2024-09-21 02:26:36 Age [y:d:h:m:s]: 00:197:00:20:25
Block: 1114643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140618 RingCT/type: yes/0
Extra: 01550dd1d49254b0aea024d36ff3ebdd65a5a63621f49c1c7fc869a80f57d8616002110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1db498bceb77c8e2c4570c6fc1de6b00d34731c6b86be10f4f5435d7f63d9f46 0.600000000000 1594496 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": 1114653, "vin": [ { "gen": { "height": 1114643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db498bceb77c8e2c4570c6fc1de6b00d34731c6b86be10f4f5435d7f63d9f46" } } ], "extra": [ 1, 85, 13, 209, 212, 146, 84, 176, 174, 160, 36, 211, 111, 243, 235, 221, 101, 165, 166, 54, 33, 244, 156, 28, 127, 200, 105, 168, 15, 87, 216, 97, 96, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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