Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d633ce11aa50b3d7929a549a7baccc96b95f405452e12781ab84e15582988f39

Tx prefix hash: f7eeaf86dd87beb1197ca8142e3275d5ec6ff1d5003d466b68b0a46fe1834089
Tx public key: 61c940b6eb38713a01284ba3a9e3105b0ed1dcc2a26b66aab97b0a4bf29adb2d
Timestamp: 1704118080 Timestamp [UCT]: 2024-01-01 14:08:00 Age [y:d:h:m:s]: 01:168:08:22:25
Block: 925879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381358 RingCT/type: yes/0
Extra: 0161c940b6eb38713a01284ba3a9e3105b0ed1dcc2a26b66aab97b0a4bf29adb2d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b2e3c8da9281c7ac3e37106741b1b76cb3fd5bdbfbba1a663b5f065ee0657b5 0.600000000000 1383649 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": 925889, "vin": [ { "gen": { "height": 925879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b2e3c8da9281c7ac3e37106741b1b76cb3fd5bdbfbba1a663b5f065ee0657b5" } } ], "extra": [ 1, 97, 201, 64, 182, 235, 56, 113, 58, 1, 40, 75, 163, 169, 227, 16, 91, 14, 209, 220, 194, 162, 107, 102, 170, 185, 123, 10, 75, 242, 154, 219, 45, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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