Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8c2181f22b32b9381862d802bc90d47ac1a85eaab4191d7234106e576577c4f

Tx prefix hash: 26bd87445cb104f5a18a99ed6939f87db30f963fd174677c25e4203ac7cf0a21
Tx public key: 00213536b3174f99d7ad2f03037b80b486cb0a95726afaa2bded056a2750e882
Timestamp: 1732501588 Timestamp [UCT]: 2024-11-25 02:26:28 Age [y:d:h:m:s]: 00:128:16:36:36
Block: 1161098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91790 RingCT/type: yes/0
Extra: 0100213536b3174f99d7ad2f03037b80b486cb0a95726afaa2bded056a2750e8820211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f8e7d2a3b64358f2510ebaf823ae595e780f02c1c9f4a2724c3f2ec6c0f4adb 0.600000000000 1646749 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": 1161108, "vin": [ { "gen": { "height": 1161098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f8e7d2a3b64358f2510ebaf823ae595e780f02c1c9f4a2724c3f2ec6c0f4adb" } } ], "extra": [ 1, 0, 33, 53, 54, 179, 23, 79, 153, 215, 173, 47, 3, 3, 123, 128, 180, 134, 203, 10, 149, 114, 106, 250, 162, 189, 237, 5, 106, 39, 80, 232, 130, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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