Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a823c2cf94b82e7280358db3c6fb1514526cf32a5975e75f2332025209a5d90d

Tx prefix hash: 293f7e3c650f7bc53b5f56da90802914c5a11ff0d1846e1974ea2833a61cb3ce
Tx public key: 818eb9a9b1161371ed370bd6e01b4b904b8b1247a54b6d402058a58c5946adce
Timestamp: 1711013502 Timestamp [UCT]: 2024-03-21 09:31:42 Age [y:d:h:m:s]: 01:054:18:38:09
Block: 983077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300126 RingCT/type: yes/0
Extra: 01818eb9a9b1161371ed370bd6e01b4b904b8b1247a54b6d402058a58c5946adce021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abb0c0dd37954cc9c890a5666f76d57bbac9f9d3cfb1604bb358cdef4acc3dea 0.600000000000 1443198 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": 983087, "vin": [ { "gen": { "height": 983077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abb0c0dd37954cc9c890a5666f76d57bbac9f9d3cfb1604bb358cdef4acc3dea" } } ], "extra": [ 1, 129, 142, 185, 169, 177, 22, 19, 113, 237, 55, 11, 214, 224, 27, 75, 144, 75, 139, 18, 71, 165, 75, 109, 64, 32, 88, 165, 140, 89, 70, 173, 206, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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