Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50185036332d8b58af7fbd694a3a27a712c93624a69a060b5d663904a076a250

Tx prefix hash: 5d58be36454a81426b780b3b456b8c5d0c2a667c811e2fc4524522a4899272e5
Tx public key: 4970cf815d47bf0f9a3db57c16771ecb132f27468fdcd2f9af891e997021d28e
Timestamp: 1712603890 Timestamp [UCT]: 2024-04-08 19:18:10 Age [y:d:h:m:s]: 01:038:07:20:24
Block: 996208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288380 RingCT/type: yes/0
Extra: 014970cf815d47bf0f9a3db57c16771ecb132f27468fdcd2f9af891e997021d28e02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 058276730bfb4b2b1a57c0a7b82e815189b1bf5cda1ee0e75624b3da4bcd40a0 0.600000000000 1456624 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": 996218, "vin": [ { "gen": { "height": 996208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "058276730bfb4b2b1a57c0a7b82e815189b1bf5cda1ee0e75624b3da4bcd40a0" } } ], "extra": [ 1, 73, 112, 207, 129, 93, 71, 191, 15, 154, 61, 181, 124, 22, 119, 30, 203, 19, 47, 39, 70, 143, 220, 210, 249, 175, 137, 30, 153, 112, 33, 210, 142, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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