Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e1033cad53923d4a5d5d15449934f1e1f4c029c8e0f44de008b7e85e2da68d8

Tx prefix hash: 1e3d66455ce6e344d3eca730f805543d3882ebcc9bd2549b4610a98535132317
Tx public key: 6ea522e5a36618c87a721a6216323893ab125ed28194b02dd0acc987887ac1e2
Timestamp: 1590457065 Timestamp [UCT]: 2020-05-26 01:37:45 Age [y:d:h:m:s]: 04:334:13:13:01
Block: 103666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164837 RingCT/type: yes/0
Extra: 016ea522e5a36618c87a721a6216323893ab125ed28194b02dd0acc987887ac1e2021100000020d81c26c0000000000000000000

1 output(s) for total of 278.309027117000 dcy

stealth address amount amount idx
00: 5126cdd6157965504d148a70a10dad2945c681c53fbb5d2d6df2a864a3412451 278.309027117000 181691 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": 103676, "vin": [ { "gen": { "height": 103666 } } ], "vout": [ { "amount": 278309027117, "target": { "key": "5126cdd6157965504d148a70a10dad2945c681c53fbb5d2d6df2a864a3412451" } } ], "extra": [ 1, 110, 165, 34, 229, 163, 102, 24, 200, 122, 114, 26, 98, 22, 50, 56, 147, 171, 18, 94, 210, 129, 148, 176, 45, 208, 172, 201, 135, 136, 122, 193, 226, 2, 17, 0, 0, 0, 32, 216, 28, 38, 192, 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