Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80b1b11c50060d74805346aee4a38131d0495945c72a36b8465bae04de6312b1

Tx prefix hash: 167c3d9641576da9a8580d6685e42d18ece80881a802c428175a048ab9fc95f3
Tx public key: 2ceaa199447df5f2cb92e4c3c5c83863a9003797dafd19f9b731b41e29c71718
Timestamp: 1703443951 Timestamp [UCT]: 2023-12-24 18:52:31 Age [y:d:h:m:s]: 01:173:23:11:39
Block: 920300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385395 RingCT/type: yes/0
Extra: 012ceaa199447df5f2cb92e4c3c5c83863a9003797dafd19f9b731b41e29c717180211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 275b53766c4698824a671fd64be5826d47e6d152217d5c148c3d6a423d8f0324 0.600000000000 1377978 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": 920310, "vin": [ { "gen": { "height": 920300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "275b53766c4698824a671fd64be5826d47e6d152217d5c148c3d6a423d8f0324" } } ], "extra": [ 1, 44, 234, 161, 153, 68, 125, 245, 242, 203, 146, 228, 195, 197, 200, 56, 99, 169, 0, 55, 151, 218, 253, 25, 249, 183, 49, 180, 30, 41, 199, 23, 24, 2, 17, 0, 0, 0, 16, 122, 156, 244, 199, 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