Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6dbdab99aba0dca3f4138afec0541566291ff184c44fa6cc066b91a44bd6c7a

Tx prefix hash: a02816248d0f385305880a674112daac4d994ef8e35adf52b81a53730f1f49b2
Tx public key: d65cd94eea8df10f1e6d320a29fd8f3b254ec29b30af6d70a71af4879a818cbc
Timestamp: 1764611046 Timestamp [UCT]: 2025-12-01 17:44:06 Age [y:d:h:m:s]: 00:057:03:34:35
Block: 1424273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40743 RingCT/type: yes/0
Extra: 01d65cd94eea8df10f1e6d320a29fd8f3b254ec29b30af6d70a71af4879a818cbc021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3af09e15831cfa30ebf4d10a763d402273400726b8745d29eb11d803f2233916 0.600000000000 1912904 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": 1424283, "vin": [ { "gen": { "height": 1424273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3af09e15831cfa30ebf4d10a763d402273400726b8745d29eb11d803f2233916" } } ], "extra": [ 1, 214, 92, 217, 78, 234, 141, 241, 15, 30, 109, 50, 10, 41, 253, 143, 59, 37, 78, 194, 155, 48, 175, 109, 112, 167, 26, 244, 135, 154, 129, 140, 188, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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