Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d28e6a8e9f9ff0ed2e12f28f7cf783508c87fc8daf93d39113224cfd8aceb26f

Tx prefix hash: d8585288949c4fae75fb9c91451a240af315d409b90a037272c6ea04140c2c46
Tx public key: 8c76a4a3238fd92f938e78c5451421e5df6f29e9a5cc237da8a1106dd8f92df4
Timestamp: 1707102852 Timestamp [UCT]: 2024-02-05 03:14:12 Age [y:d:h:m:s]: 01:067:15:09:36
Block: 950618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309402 RingCT/type: yes/0
Extra: 018c76a4a3238fd92f938e78c5451421e5df6f29e9a5cc237da8a1106dd8f92df40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a5be83669d820f38c2650bda730d767e14f9dc661f129305affa38de8414c0 0.600000000000 1409264 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": 950628, "vin": [ { "gen": { "height": 950618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a5be83669d820f38c2650bda730d767e14f9dc661f129305affa38de8414c0" } } ], "extra": [ 1, 140, 118, 164, 163, 35, 143, 217, 47, 147, 142, 120, 197, 69, 20, 33, 229, 223, 111, 41, 233, 165, 204, 35, 125, 168, 161, 16, 109, 216, 249, 45, 244, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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