Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e81a934db61786c0e0a100b0792af0d6de6933f329308b957cb95c365cf6b445

Tx prefix hash: 0dc5c0890367c81c22ee1624c29244f540176fef01703f0f62e2573361c820e9
Tx public key: 96fdee2784b8e993810a1e12ed273f8e7a523c1b6bb486d9a2ea81513625dc30
Timestamp: 1649747143 Timestamp [UCT]: 2022-04-12 07:05:43 Age [y:d:h:m:s]: 02:308:04:44:37
Block: 478449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 739899 RingCT/type: yes/0
Extra: 0196fdee2784b8e993810a1e12ed273f8e7a523c1b6bb486d9a2ea81513625dc30021100000002cb8520c2000000000000000000

1 output(s) for total of 15.947774511000 dcy

stealth address amount amount idx
00: e2e6a214d7e38cb2362e53abd71850b077ef530551275cd00e488b2b383585c4 15.947774511000 899216 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": 478459, "vin": [ { "gen": { "height": 478449 } } ], "vout": [ { "amount": 15947774511, "target": { "key": "e2e6a214d7e38cb2362e53abd71850b077ef530551275cd00e488b2b383585c4" } } ], "extra": [ 1, 150, 253, 238, 39, 132, 184, 233, 147, 129, 10, 30, 18, 237, 39, 63, 142, 122, 82, 60, 27, 107, 180, 134, 217, 162, 234, 129, 81, 54, 37, 220, 48, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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