Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce2028df4bdeaf69f28e0fb224adfd3439b39e6619b9cde43daaf117f9108b98

Tx prefix hash: 467d0ad90d5fa84fb609d7982450bc7f1f7326b5d40c08cb732ddaeac2580186
Tx public key: e79ee866a315e38e8c2e98a97a87f7898deb1f6126dca895fc9827f5af5e3c84
Timestamp: 1761666110 Timestamp [UCT]: 2025-10-28 15:41:50 Age [y:d:h:m:s]: 00:017:02:42:36
Block: 1399878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12243 RingCT/type: yes/0
Extra: 01e79ee866a315e38e8c2e98a97a87f7898deb1f6126dca895fc9827f5af5e3c8402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0038021a39ea6732a97be8e4fa5f73557f4a9a7f79efd154663e4bf386ffd98 0.600000000000 1888185 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": 1399888, "vin": [ { "gen": { "height": 1399878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0038021a39ea6732a97be8e4fa5f73557f4a9a7f79efd154663e4bf386ffd98" } } ], "extra": [ 1, 231, 158, 232, 102, 163, 21, 227, 142, 140, 46, 152, 169, 122, 135, 247, 137, 141, 235, 31, 97, 38, 220, 168, 149, 252, 152, 39, 245, 175, 94, 60, 132, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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