Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f801581c9cd7547d89d41419b4c225a2532b3825d75e840577ffbb357b0674c

Tx prefix hash: 350f9fe79eb54a5e5d55fa47fa3b8e99cb2cb19b1f229ce4b047a46a640c92b8
Tx public key: 717167ac152f9b2598df681ee9c414c93aa690806988a098170fdeec35aad4a2
Timestamp: 1733907316 Timestamp [UCT]: 2024-12-11 08:55:16 Age [y:d:h:m:s]: 00:110:03:49:23
Block: 1172752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78524 RingCT/type: yes/0
Extra: 01717167ac152f9b2598df681ee9c414c93aa690806988a098170fdeec35aad4a2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dc6503cf087f8645ea53c5dbb5d4bbdff938dbf8c7a94d3ba1747c898bd78de 0.600000000000 1658683 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": 1172762, "vin": [ { "gen": { "height": 1172752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dc6503cf087f8645ea53c5dbb5d4bbdff938dbf8c7a94d3ba1747c898bd78de" } } ], "extra": [ 1, 113, 113, 103, 172, 21, 47, 155, 37, 152, 223, 104, 30, 233, 196, 20, 201, 58, 166, 144, 128, 105, 136, 160, 152, 23, 15, 222, 236, 53, 170, 212, 162, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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