Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a7f1c0b1b880fc0ac059e748860c4be7e1a4cac1eca3cdd7b644b424b4b3f38

Tx prefix hash: 0f0f52e998b105f31b762da9a1540e9929e2e8e345114b0f57a336bd702983f3
Tx public key: 6f86941b2890dc2a87231f8e3da4d23dc106950518d41fe2c2c7b5c06edc0f4d
Timestamp: 1710937632 Timestamp [UCT]: 2024-03-20 12:27:12 Age [y:d:h:m:s]: 01:017:03:59:34
Block: 982445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273220 RingCT/type: yes/0
Extra: 016f86941b2890dc2a87231f8e3da4d23dc106950518d41fe2c2c7b5c06edc0f4d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5024540cc752a9e1965627e322efdc22f91c27be9715784c6d57184b066e5450 0.600000000000 1442550 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": 982455, "vin": [ { "gen": { "height": 982445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5024540cc752a9e1965627e322efdc22f91c27be9715784c6d57184b066e5450" } } ], "extra": [ 1, 111, 134, 148, 27, 40, 144, 220, 42, 135, 35, 31, 142, 61, 164, 210, 61, 193, 6, 149, 5, 24, 212, 31, 226, 194, 199, 181, 192, 110, 220, 15, 77, 2, 17, 0, 0, 0, 1, 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