Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fa0c28584d1205cbf3d5b19889dea7743f27b23c1c906ce9291bb553636fb9a

Tx prefix hash: 37c6fa2041d2664f79a9725beeec0f714952444a78dc825b632c4ef7bfa0b3a4
Tx public key: ce8a0cfb29053f2aaab4ff6a72416ad4a55c79395f6c82e32846b5a941b03fee
Timestamp: 1749490041 Timestamp [UCT]: 2025-06-09 17:27:21 Age [y:d:h:m:s]: 00:154:07:46:06
Block: 1301494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107959 RingCT/type: yes/0
Extra: 01ce8a0cfb29053f2aaab4ff6a72416ad4a55c79395f6c82e32846b5a941b03fee021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a56646ec264fee21e4bb96733121d60e31abe4a5b42281ee750192a0ec8b731d 0.600000000000 1789053 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": 1301504, "vin": [ { "gen": { "height": 1301494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a56646ec264fee21e4bb96733121d60e31abe4a5b42281ee750192a0ec8b731d" } } ], "extra": [ 1, 206, 138, 12, 251, 41, 5, 63, 42, 170, 180, 255, 106, 114, 65, 106, 212, 165, 92, 121, 57, 95, 108, 130, 227, 40, 70, 181, 169, 65, 176, 63, 238, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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