Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4895bc1dc7952489c81ff76ee4ad1a36903c1b65961e451ff581280d82f1156e

Tx prefix hash: 12e286a2bfd7e9e69b93a3856fd455bf463f897a33f37e10b48eeb8c490a4b6a
Tx public key: f21b222f63f74ce9f08f542689b50f667cc73a2528b26048b2325c7c31c36a41
Timestamp: 1582512138 Timestamp [UCT]: 2020-02-24 02:42:18 Age [y:d:h:m:s]: 04:280:08:54:27
Block: 71235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093000 RingCT/type: yes/0
Extra: 01f21b222f63f74ce9f08f542689b50f667cc73a2528b26048b2325c7c31c36a4102110000000203d36d11000000000000000000

1 output(s) for total of 356.448105445000 dcy

stealth address amount amount idx
00: e6173fea53f549756b92cf7e992047edf26a84a62bfe5dcec36a4255ad9cb4a6 356.448105445000 131623 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": 71245, "vin": [ { "gen": { "height": 71235 } } ], "vout": [ { "amount": 356448105445, "target": { "key": "e6173fea53f549756b92cf7e992047edf26a84a62bfe5dcec36a4255ad9cb4a6" } } ], "extra": [ 1, 242, 27, 34, 47, 99, 247, 76, 233, 240, 143, 84, 38, 137, 181, 15, 102, 124, 199, 58, 37, 40, 178, 96, 72, 178, 50, 92, 124, 49, 195, 106, 65, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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