Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba7c1e5bcdfb11898a874f2c9134ee3b828c242eb9e1cbe3298a47d5801a9b6d

Tx prefix hash: 9f08d44f3da86e23c08bd01a2c72baa799dbf49e06619e0f04c1d9d99fe74d0e
Tx public key: d5a207e963fee4928e34e8e8ca14735aeb36cdd42bfbf8f15783a567d9f64a07
Timestamp: 1576425662 Timestamp [UCT]: 2019-12-15 16:01:02 Age [y:d:h:m:s]: 04:347:04:21:15
Block: 27571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134062 RingCT/type: yes/0
Extra: 01d5a207e963fee4928e34e8e8ca14735aeb36cdd42bfbf8f15783a567d9f64a070211000000499159db1e000000000000000000

1 output(s) for total of 497.332336090000 dcy

stealth address amount amount idx
00: 4b197c6a056806b2d9508aef578449bfdf7857b68e8d8fda2f57f1333feaf837 497.332336090000 45583 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": 27581, "vin": [ { "gen": { "height": 27571 } } ], "vout": [ { "amount": 497332336090, "target": { "key": "4b197c6a056806b2d9508aef578449bfdf7857b68e8d8fda2f57f1333feaf837" } } ], "extra": [ 1, 213, 162, 7, 233, 99, 254, 228, 146, 142, 52, 232, 232, 202, 20, 115, 90, 235, 54, 205, 212, 43, 251, 248, 241, 87, 131, 165, 103, 217, 246, 74, 7, 2, 17, 0, 0, 0, 73, 145, 89, 219, 30, 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