Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26937d18793f0fdf914f8b5e8b815b01ebc5f5436a58c0fe82623fa96b96eacf

Tx prefix hash: f882e1e5a5571889b398458862f23ed9e1688c7511b76121597fbc111a77aaad
Tx public key: 399ae40a9375ff49bd27a0d7a6759d9a4e69e77b711700675b3487999f8af464
Timestamp: 1746190241 Timestamp [UCT]: 2025-05-02 12:50:41 Age [y:d:h:m:s]: 00:203:09:20:36
Block: 1274160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143080 RingCT/type: yes/0
Extra: 01399ae40a9375ff49bd27a0d7a6759d9a4e69e77b711700675b3487999f8af4640211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aee278a20293a359454c1b8da7472dda3dd0d4743a47fb1bd9fadf8d847e7fc 0.600000000000 1761451 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": 1274170, "vin": [ { "gen": { "height": 1274160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aee278a20293a359454c1b8da7472dda3dd0d4743a47fb1bd9fadf8d847e7fc" } } ], "extra": [ 1, 57, 154, 228, 10, 147, 117, 255, 73, 189, 39, 160, 215, 166, 117, 157, 154, 78, 105, 231, 123, 113, 23, 0, 103, 91, 52, 135, 153, 159, 138, 244, 100, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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