Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1100afdaafb6d0612029c76590112e62fe585f0cb088b0bcf3d019b4ac406e

Tx prefix hash: 52418bf54e6e78ca3f55fe5a717ed3104e9899f2e820fa44be6529e846ba67ab
Tx public key: 176acb42e6e000d864f6c55aa49681fe5a311340982dff1145229f256a43b3c3
Timestamp: 1609363438 Timestamp [UCT]: 2020-12-30 21:23:58 Age [y:d:h:m:s]: 03:321:20:28:44
Block: 172338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 982778 RingCT/type: yes/0
Extra: 01176acb42e6e000d864f6c55aa49681fe5a311340982dff1145229f256a43b3c302110000007527e2517e000000000000000000

1 output(s) for total of 164.806117141000 dcy

stealth address amount amount idx
00: 7b40260a8b497f684974aa9ccd4c1d71cf5d7380619a363ac7b0c90dafc6ab9e 164.806117141000 325813 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": 172348, "vin": [ { "gen": { "height": 172338 } } ], "vout": [ { "amount": 164806117141, "target": { "key": "7b40260a8b497f684974aa9ccd4c1d71cf5d7380619a363ac7b0c90dafc6ab9e" } } ], "extra": [ 1, 23, 106, 203, 66, 230, 224, 0, 216, 100, 246, 197, 90, 164, 150, 129, 254, 90, 49, 19, 64, 152, 45, 255, 17, 69, 34, 159, 37, 106, 67, 179, 195, 2, 17, 0, 0, 0, 117, 39, 226, 81, 126, 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