Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34eb7ca81ba1bd98d53e57c8289b4285272eca9a4cd098f7e018e05a0834e6e9

Tx prefix hash: adda86e392d7de379ae6b6fc465713cf6d4dc9494ab505c6c16d5abb1cd5d3e7
Tx public key: 9b42e4a76fa0ad61f3470c0dad53d1f957fd7595942505e6b604843d76e18986
Timestamp: 1707440619 Timestamp [UCT]: 2024-02-09 01:03:39 Age [y:d:h:m:s]: 01:055:12:43:06
Block: 953420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300739 RingCT/type: yes/0
Extra: 019b42e4a76fa0ad61f3470c0dad53d1f957fd7595942505e6b604843d76e1898602110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f36839734a8d9ace2233bd88e5151ea795d2a667b0e436015a4576f86bc1d096 0.600000000000 1412624 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": 953430, "vin": [ { "gen": { "height": 953420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f36839734a8d9ace2233bd88e5151ea795d2a667b0e436015a4576f86bc1d096" } } ], "extra": [ 1, 155, 66, 228, 167, 111, 160, 173, 97, 243, 71, 12, 13, 173, 83, 209, 249, 87, 253, 117, 149, 148, 37, 5, 230, 182, 4, 132, 61, 118, 225, 137, 134, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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