Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88c171641e5150fcc998fbf27bfcdd6a1370a6781771138d326ccbfac69d2af8

Tx prefix hash: 657b22d2419086f9d5507ed9ed5be55d1e34e7e586c8d94c436b91ca88439b29
Tx public key: bbc793d1e810fc730be57e0151704c7cff97a92beed742f8af5bbda93bc1d5f1
Timestamp: 1678933504 Timestamp [UCT]: 2023-03-16 02:25:04 Age [y:d:h:m:s]: 01:310:09:55:11
Block: 717991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482716 RingCT/type: yes/0
Extra: 01bbc793d1e810fc730be57e0151704c7cff97a92beed742f8af5bbda93bc1d5f10211000000045029cbac000000000000000000

1 output(s) for total of 2.564470170000 dcy

stealth address amount amount idx
00: e8f5476476d8e7184d857a46b9bfea0d03b0b5cda169eabf6aa83fa3558829c0 2.564470170000 1162628 of 0

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": 718001, "vin": [ { "gen": { "height": 717991 } } ], "vout": [ { "amount": 2564470170, "target": { "key": "e8f5476476d8e7184d857a46b9bfea0d03b0b5cda169eabf6aa83fa3558829c0" } } ], "extra": [ 1, 187, 199, 147, 209, 232, 16, 252, 115, 11, 229, 126, 1, 81, 112, 76, 124, 255, 151, 169, 43, 238, 215, 66, 248, 175, 91, 189, 169, 59, 193, 213, 241, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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