Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0513079b6d1b29fe6799e87d327fc713a3064cbecb7137c46b9625ce3fc5de

Tx prefix hash: d3be5c4e780e1b4d46980acf1ff34e905420f5333225bca5423cc0f08110656d
Tx public key: 879a4a6d7fccc3b4796eb3876086838f42b87e3e9b4a5e56cf8fb4792a79b239
Timestamp: 1721694094 Timestamp [UCT]: 2024-07-23 00:21:34 Age [y:d:h:m:s]: 00:281:20:10:21
Block: 1071586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201367 RingCT/type: yes/0
Extra: 01879a4a6d7fccc3b4796eb3876086838f42b87e3e9b4a5e56cf8fb4792a79b23902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b46f8f107dc9f74c5955d8405a042079db34ba573c64581e4eef905972e12d4 0.600000000000 1543871 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": 1071596, "vin": [ { "gen": { "height": 1071586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b46f8f107dc9f74c5955d8405a042079db34ba573c64581e4eef905972e12d4" } } ], "extra": [ 1, 135, 154, 74, 109, 127, 204, 195, 180, 121, 110, 179, 135, 96, 134, 131, 143, 66, 184, 126, 62, 155, 74, 94, 86, 207, 143, 180, 121, 42, 121, 178, 57, 2, 17, 0, 0, 0, 2, 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