Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51b946398162923fd9194fad743ff45c8b0e8113fbf410fb7b0c82e23564a65c

Tx prefix hash: 9547fd4048ed352b0b6a0af26f72d4c1beefef36a3851d1486624f5b16c6d0ab
Tx public key: 0f5475cc386b3686630d8e5267b34463dfb337096acdc0d3fbb6322a78f2cfe1
Timestamp: 1718552903 Timestamp [UCT]: 2024-06-16 15:48:23 Age [y:d:h:m:s]: 00:288:08:03:17
Block: 1045574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206030 RingCT/type: yes/0
Extra: 010f5475cc386b3686630d8e5267b34463dfb337096acdc0d3fbb6322a78f2cfe10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97c832c4cb84b8bd853279e5a639916060817eb712458a71b798ba22839b56f5 0.600000000000 1515181 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": 1045584, "vin": [ { "gen": { "height": 1045574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97c832c4cb84b8bd853279e5a639916060817eb712458a71b798ba22839b56f5" } } ], "extra": [ 1, 15, 84, 117, 204, 56, 107, 54, 134, 99, 13, 142, 82, 103, 179, 68, 99, 223, 179, 55, 9, 106, 205, 192, 211, 251, 182, 50, 42, 120, 242, 207, 225, 2, 17, 0, 0, 0, 1, 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