Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab63c20d7a3dab8994c7d0e766189e9a487f392ef1adec8c68840232b4a8fce8

Tx prefix hash: c797b548b216a2b63b9b436be2ffe821c766bf01d522b245a4e274c95f6062e0
Tx public key: eece6b1e828fb588bc0aeca204a0b8f70211c146158dbe5a104093bdaa873280
Timestamp: 1712684782 Timestamp [UCT]: 2024-04-09 17:46:22 Age [y:d:h:m:s]: 01:012:20:39:01
Block: 996889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270165 RingCT/type: yes/0
Extra: 01eece6b1e828fb588bc0aeca204a0b8f70211c146158dbe5a104093bdaa873280021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0ce52117c322a48c968c02c9aa4f524b9c93f916f9bb4e845c6ce2768a20ee0 0.600000000000 1457317 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": 996899, "vin": [ { "gen": { "height": 996889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0ce52117c322a48c968c02c9aa4f524b9c93f916f9bb4e845c6ce2768a20ee0" } } ], "extra": [ 1, 238, 206, 107, 30, 130, 143, 181, 136, 188, 10, 236, 162, 4, 160, 184, 247, 2, 17, 193, 70, 21, 141, 190, 90, 16, 64, 147, 189, 170, 135, 50, 128, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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