Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 508b7c26582244456e84c723dc65751ac1479f357feb49175fb287d7650b0544

Tx prefix hash: e86d798b9fbf850d3d829ddfbdc982b496dc6c7f596db0f1465ce6cfdc4080c4
Tx public key: 628602c818eee0dbe3c96b273512e95d74a82f184e35aa26ab5a95d5d1e5513f
Timestamp: 1695765828 Timestamp [UCT]: 2023-09-26 22:03:48 Age [y:d:h:m:s]: 01:197:00:58:41
Block: 856839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401887 RingCT/type: yes/0
Extra: 01628602c818eee0dbe3c96b273512e95d74a82f184e35aa26ab5a95d5d1e5513f0211000000104b8f5122000000000000000000

1 output(s) for total of 0.889071623000 dcy

stealth address amount amount idx
00: c7863c79585c99a0bbfdbfe9b57e077a7a2ab57514721a3e1191a1bde9356b40 0.889071623000 1310931 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": 856849, "vin": [ { "gen": { "height": 856839 } } ], "vout": [ { "amount": 889071623, "target": { "key": "c7863c79585c99a0bbfdbfe9b57e077a7a2ab57514721a3e1191a1bde9356b40" } } ], "extra": [ 1, 98, 134, 2, 200, 24, 238, 224, 219, 227, 201, 107, 39, 53, 18, 233, 93, 116, 168, 47, 24, 78, 53, 170, 38, 171, 90, 149, 213, 209, 229, 81, 63, 2, 17, 0, 0, 0, 16, 75, 143, 81, 34, 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