Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd234c7e940fa572ab60ff40f8aef05a63585c863fad1a8b5eb55a9206571762

Tx prefix hash: 017b7d35f48990914f097f293a18d5f16eb9aaa33f7ccf937ba18018835f37d1
Tx public key: 478c7ecef2d852c5259c4f728694638cb0a6863e89ba726aeb86b2b995246a96
Timestamp: 1761719206 Timestamp [UCT]: 2025-10-29 06:26:46 Age [y:d:h:m:s]: 00:012:15:07:36
Block: 1400322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9029 RingCT/type: yes/0
Extra: 01478c7ecef2d852c5259c4f728694638cb0a6863e89ba726aeb86b2b995246a9602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f358fbe922e9eda297279db2a1f2badc90ec0b9a8dca04052aa80dec7f9df5b 0.600000000000 1888629 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": 1400332, "vin": [ { "gen": { "height": 1400322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f358fbe922e9eda297279db2a1f2badc90ec0b9a8dca04052aa80dec7f9df5b" } } ], "extra": [ 1, 71, 140, 126, 206, 242, 216, 82, 197, 37, 156, 79, 114, 134, 148, 99, 140, 176, 166, 134, 62, 137, 186, 114, 106, 235, 134, 178, 185, 149, 36, 106, 150, 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