Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 896c512ed9f613c0fb19725ef608f0c9154eeb0e940d40d41d36fc65df246576

Tx prefix hash: cffdf00b34cc21dd5b056dcf996066165fe18097a0de751942ca2cbb5df22024
Tx public key: 699f250dbfb0c1243eb838ffa6f5868c2ab81abc276f382702e3a749af08bd55
Timestamp: 1608323356 Timestamp [UCT]: 2020-12-18 20:29:16 Age [y:d:h:m:s]: 03:346:22:11:20
Block: 164705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 999752 RingCT/type: yes/0
Extra: 01699f250dbfb0c1243eb838ffa6f5868c2ab81abc276f382702e3a749af08bd550211000006e84ea414e5000000000000000000

1 output(s) for total of 174.692748943000 dcy

stealth address amount amount idx
00: a5a01e13bd8f682dd051cb82d78c28ec67149b7e3824d9e1e0d175d17816aa6e 174.692748943000 298340 of 0

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": 164715, "vin": [ { "gen": { "height": 164705 } } ], "vout": [ { "amount": 174692748943, "target": { "key": "a5a01e13bd8f682dd051cb82d78c28ec67149b7e3824d9e1e0d175d17816aa6e" } } ], "extra": [ 1, 105, 159, 37, 13, 191, 176, 193, 36, 62, 184, 56, 255, 166, 245, 134, 140, 42, 184, 26, 188, 39, 111, 56, 39, 2, 227, 167, 73, 175, 8, 189, 85, 2, 17, 0, 0, 6, 232, 78, 164, 20, 229, 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