Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61861d1d10ce54109134a3cca4ec4b8b25170193285c818f01bf606121d29f76

Tx prefix hash: 766a1a1754c1f3039f86336b8763154d06bc8bfd65285663174e5e5c5c7e4f82
Tx public key: 62f9bfe8d654f6226962f69ed7e78f777a5e8231a9173dea6e1b72db8bd1c4f5
Timestamp: 1723363821 Timestamp [UCT]: 2024-08-11 08:10:21 Age [y:d:h:m:s]: 00:281:13:28:45
Block: 1085449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201138 RingCT/type: yes/0
Extra: 0162f9bfe8d654f6226962f69ed7e78f777a5e8231a9173dea6e1b72db8bd1c4f5021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f1792d625518ad25afad99516115befa17b332e9d50500ce6c3280a16a40d5d 0.600000000000 1560032 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": 1085459, "vin": [ { "gen": { "height": 1085449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f1792d625518ad25afad99516115befa17b332e9d50500ce6c3280a16a40d5d" } } ], "extra": [ 1, 98, 249, 191, 232, 214, 84, 246, 34, 105, 98, 246, 158, 215, 231, 143, 119, 122, 94, 130, 49, 169, 23, 61, 234, 110, 27, 114, 219, 139, 209, 196, 245, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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