Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 185c2bb0878a8247af7c04c0e23fc70a321a04dbd182809badbd288dc83479f2

Tx prefix hash: 8288c204460e222d7bf83c5165f21d48f761ec6d3e4f1fd61fed1e5684fdfdd0
Tx public key: fd4b89b9ab6b3aa8b8331ae0dd5f2fb75070256d4e239512c29890c66865cc1c
Timestamp: 1711444308 Timestamp [UCT]: 2024-03-26 09:11:48 Age [y:d:h:m:s]: 01:007:07:15:23
Block: 986648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266162 RingCT/type: yes/0
Extra: 01fd4b89b9ab6b3aa8b8331ae0dd5f2fb75070256d4e239512c29890c66865cc1c0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f97486079219943595f76390ace013fd30ea743ab912442d0abccb9e124b0ec5 0.600000000000 1446879 of 15

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": 986658, "vin": [ { "gen": { "height": 986648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f97486079219943595f76390ace013fd30ea743ab912442d0abccb9e124b0ec5" } } ], "extra": [ 1, 253, 75, 137, 185, 171, 107, 58, 168, 184, 51, 26, 224, 221, 95, 47, 183, 80, 112, 37, 109, 78, 35, 149, 18, 194, 152, 144, 198, 104, 101, 204, 28, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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