Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee46a8bf12e30ea6cdcc1603284aaadd3c810a2285b6ac54ec3343038c92cfa4

Tx prefix hash: 0947d5c70121caab24078f136e5f534d8dc1def4aa481efa4388cfaea0b5f5a7
Tx public key: d35fbd024dc247ec2cd49ff7814979f0c6eed7c0db6640b8e8e74ee62618b366
Timestamp: 1704200517 Timestamp [UCT]: 2024-01-02 13:01:57 Age [y:d:h:m:s]: 01:310:05:24:44
Block: 926559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480551 RingCT/type: yes/0
Extra: 01d35fbd024dc247ec2cd49ff7814979f0c6eed7c0db6640b8e8e74ee62618b36602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a60112c75b9f9f6e82df69287bd3a13815317879ba7905f8dee427ff7b7fbbe4 0.600000000000 1384353 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": 926569, "vin": [ { "gen": { "height": 926559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a60112c75b9f9f6e82df69287bd3a13815317879ba7905f8dee427ff7b7fbbe4" } } ], "extra": [ 1, 211, 95, 189, 2, 77, 194, 71, 236, 44, 212, 159, 247, 129, 73, 121, 240, 198, 238, 215, 192, 219, 102, 64, 184, 232, 231, 78, 230, 38, 24, 179, 102, 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