Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389dc7d69e87e850475633f8dbf22b17d4949577c424aa460cfb9030fb18f319

Tx prefix hash: 8653e8a8312f1927159db672b660a4a61383fb1c1581f1d2897c6aa2a59766e1
Tx public key: 63509e0f6181863d1b9287ac964c34ef6aa979408a9f7e6ac251105342da93d5
Timestamp: 1577735156 Timestamp [UCT]: 2019-12-30 19:45:56 Age [y:d:h:m:s]: 05:016:19:54:59
Block: 35288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161973 RingCT/type: yes/0
Extra: 0163509e0f6181863d1b9287ac964c34ef6aa979408a9f7e6ac251105342da93d502110000000a78873133000000000000000000

1 output(s) for total of 468.896576397000 dcy

stealth address amount amount idx
00: 84a4aa91ead8d6b7308e0b65d32c88b95d300757cbbab290faf5599dadcf77e0 468.896576397000 59434 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": 35298, "vin": [ { "gen": { "height": 35288 } } ], "vout": [ { "amount": 468896576397, "target": { "key": "84a4aa91ead8d6b7308e0b65d32c88b95d300757cbbab290faf5599dadcf77e0" } } ], "extra": [ 1, 99, 80, 158, 15, 97, 129, 134, 61, 27, 146, 135, 172, 150, 76, 52, 239, 106, 169, 121, 64, 138, 159, 126, 106, 194, 81, 16, 83, 66, 218, 147, 213, 2, 17, 0, 0, 0, 10, 120, 135, 49, 51, 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