Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f1fcce7fc53c257e4e81fff982d45b99de096d67a905aaeebe418fdcbd3a0b6

Tx prefix hash: b8e82425ac435ee9a87fbf768f180709487be53de6172d0c5893f92644d623d8
Tx public key: 28efead6a14921975081d4dab05f8ee85b9577b576a287a36fcfa4edf1a33ea1
Timestamp: 1708085039 Timestamp [UCT]: 2024-02-16 12:03:59 Age [y:d:h:m:s]: 01:047:22:14:20
Block: 958770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295295 RingCT/type: yes/0
Extra: 0128efead6a14921975081d4dab05f8ee85b9577b576a287a36fcfa4edf1a33ea10211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8039adc189b6ad84a8bbd3afe8b174dca2cf266b805fa399eab40d683f8d463c 0.600000000000 1418131 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": 958780, "vin": [ { "gen": { "height": 958770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8039adc189b6ad84a8bbd3afe8b174dca2cf266b805fa399eab40d683f8d463c" } } ], "extra": [ 1, 40, 239, 234, 214, 161, 73, 33, 151, 80, 129, 212, 218, 176, 95, 142, 232, 91, 149, 119, 181, 118, 162, 135, 163, 111, 207, 164, 237, 241, 163, 62, 161, 2, 17, 0, 0, 0, 7, 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