Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ef50e6f636d8fa377d3caa61335fc609ea4c51c5b2f63d7f8b08333a9a9d2ee

Tx prefix hash: 1acd10d9fbb8245a937785516c1b2a65fdd22286641325e6095aa4e722170de9
Tx public key: 544940a0a9cea02525a2215f644cb492d470dabd8ca7c1a2f4f41c35764e0e86
Timestamp: 1725757397 Timestamp [UCT]: 2024-09-08 01:03:17 Age [y:d:h:m:s]: 00:238:18:00:52
Block: 1105286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170487 RingCT/type: yes/0
Extra: 01544940a0a9cea02525a2215f644cb492d470dabd8ca7c1a2f4f41c35764e0e86021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ad435d91778ed54d5f7820e5113b28ace44b68ea2fa12c481ec174c7287bffc 0.600000000000 1582627 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": 1105296, "vin": [ { "gen": { "height": 1105286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ad435d91778ed54d5f7820e5113b28ace44b68ea2fa12c481ec174c7287bffc" } } ], "extra": [ 1, 84, 73, 64, 160, 169, 206, 160, 37, 37, 162, 33, 95, 100, 76, 180, 146, 212, 112, 218, 189, 140, 167, 193, 162, 244, 244, 28, 53, 118, 78, 14, 134, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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