Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a9dcb90f45cef97b5f5b600675272cc2ee5c1837070593f952604b3f2fba579

Tx prefix hash: 096f550593dcb0e61486d371c1b822699bd9c1957fb0fca20e41f5e11f4c1cff
Tx public key: bff9d31c6e5857bdcbb3604a4c1d1c6bbb7cef6536e99d72eb19dfb924909613
Timestamp: 1574652726 Timestamp [UCT]: 2019-11-25 03:32:06 Age [y:d:h:m:s]: 04:361:00:01:08
Block: 16867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139980 RingCT/type: yes/0
Extra: 01bff9d31c6e5857bdcbb3604a4c1d1c6bbb7cef6536e99d72eb19dfb924909613021100000001f95225a5000000000000000000

1 output(s) for total of 539.651649166000 dcy

stealth address amount amount idx
00: b63dc7e55f0339a4c7dd212b5ce4a87acb46319164fdb93176a8c20ab874d1cb 539.651649166000 23951 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": 16877, "vin": [ { "gen": { "height": 16867 } } ], "vout": [ { "amount": 539651649166, "target": { "key": "b63dc7e55f0339a4c7dd212b5ce4a87acb46319164fdb93176a8c20ab874d1cb" } } ], "extra": [ 1, 191, 249, 211, 28, 110, 88, 87, 189, 203, 179, 96, 74, 76, 29, 28, 107, 187, 124, 239, 101, 54, 233, 157, 114, 235, 25, 223, 185, 36, 144, 150, 19, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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