Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fc63d4c9f34cf0df132386a00822aed84e960ae31a0ece5f0b3ce9d0fc766e3

Tx prefix hash: d92acaeb1e25eb197970c103d72591cce2639fec96e31fac4043b9e859be383c
Tx public key: 297943804d3e9c8e86a4dbd826a3c7c5768665ae58accc4422a736b58411d3a2
Timestamp: 1728116866 Timestamp [UCT]: 2024-10-05 08:27:46 Age [y:d:h:m:s]: 00:159:22:17:28
Block: 1124844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114105 RingCT/type: yes/0
Extra: 01297943804d3e9c8e86a4dbd826a3c7c5768665ae58accc4422a736b58411d3a202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 381d0b0ffff0f820a61bfeb3acdc0c9179bc04f3bea624a45d0e4b69b2d47ca5 0.600000000000 1607515 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": 1124854, "vin": [ { "gen": { "height": 1124844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "381d0b0ffff0f820a61bfeb3acdc0c9179bc04f3bea624a45d0e4b69b2d47ca5" } } ], "extra": [ 1, 41, 121, 67, 128, 77, 62, 156, 142, 134, 164, 219, 216, 38, 163, 199, 197, 118, 134, 101, 174, 88, 172, 204, 68, 34, 167, 54, 181, 132, 17, 211, 162, 2, 17, 0, 0, 0, 3, 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