Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 691d80a8bb1ac27ffb2f584476de9303c5ea2a1272461c0917032b160a12379e

Tx prefix hash: a21562227d9b26a2431e44d2b34385a0a1b0c0d4845899242195d32510061b99
Tx public key: 3cc7465696748b746e818a61a8e1f9e95f760072657ee2df2dd77053c40030b4
Timestamp: 1748828820 Timestamp [UCT]: 2025-06-02 01:47:00 Age [y:d:h:m:s]: 00:171:03:38:24
Block: 1296024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120008 RingCT/type: yes/0
Extra: 013cc7465696748b746e818a61a8e1f9e95f760072657ee2df2dd77053c40030b4021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d17e55564e930c865d6c2a86d7d8a5278d91cb70e1db77119b95c6d0c60b1c0 0.600000000000 1783531 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": 1296034, "vin": [ { "gen": { "height": 1296024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d17e55564e930c865d6c2a86d7d8a5278d91cb70e1db77119b95c6d0c60b1c0" } } ], "extra": [ 1, 60, 199, 70, 86, 150, 116, 139, 116, 110, 129, 138, 97, 168, 225, 249, 233, 95, 118, 0, 114, 101, 126, 226, 223, 45, 215, 112, 83, 196, 0, 48, 180, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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