Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 186493b20d89efb33842e2c7f9f4205a32758795b4168b92bdd84fb7bf688bc6

Tx prefix hash: 083d08a03cac859807dfeaffdf4b32b0da59ce86893abd911eea087301dddd41
Tx public key: 27de107d6fb3a82b6813a2d0b00261bcde95432dcc0b0b1b2c2afa1e8d8524e6
Timestamp: 1723305412 Timestamp [UCT]: 2024-08-10 15:56:52 Age [y:d:h:m:s]: 00:106:14:36:44
Block: 1084961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76262 RingCT/type: yes/0
Extra: 0127de107d6fb3a82b6813a2d0b00261bcde95432dcc0b0b1b2c2afa1e8d8524e602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28ea8ac7cd1688137b3623137cb9606896157c6a37e14a4642d83ee7a73f6506 0.600000000000 1559420 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": 1084971, "vin": [ { "gen": { "height": 1084961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28ea8ac7cd1688137b3623137cb9606896157c6a37e14a4642d83ee7a73f6506" } } ], "extra": [ 1, 39, 222, 16, 125, 111, 179, 168, 43, 104, 19, 162, 208, 176, 2, 97, 188, 222, 149, 67, 45, 204, 11, 11, 27, 44, 42, 250, 30, 141, 133, 36, 230, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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