Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848a060a7a8a689087248c1159b22b7078502119d30a2509890418a588e8d1dd

Tx prefix hash: 7f0f48da9c1eac0ae9d2d45e3da0b7b383919fd9b9e802507021f4fb5073ba07
Tx public key: 46e211714d2a4cd1d9bb10efe50e5fb6703438b0fb996b27f986ebabba204ca0
Timestamp: 1730356314 Timestamp [UCT]: 2024-10-31 06:31:54 Age [y:d:h:m:s]: 00:058:02:32:33
Block: 1143335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41574 RingCT/type: yes/0
Extra: 0146e211714d2a4cd1d9bb10efe50e5fb6703438b0fb996b27f986ebabba204ca00211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21f4211ea5b7c6411440a2ba476188e14f90c231595dbcfe0c84fd47bf8b3c83 0.600000000000 1627198 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": 1143345, "vin": [ { "gen": { "height": 1143335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21f4211ea5b7c6411440a2ba476188e14f90c231595dbcfe0c84fd47bf8b3c83" } } ], "extra": [ 1, 70, 226, 17, 113, 77, 42, 76, 209, 217, 187, 16, 239, 229, 14, 95, 182, 112, 52, 56, 176, 251, 153, 107, 39, 249, 134, 235, 171, 186, 32, 76, 160, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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