Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f65a98ffcc97f08ffb0f9c75bbec64975c715891be7eb1d206ae59544c32a635

Tx prefix hash: 8e0c43f7342708cdbcc0d1ad936d0b04e2bfa9cb0c89c79077aa1829c1d0fce1
Tx public key: 674570e1dcd49fbd224df0f54660792b51c69899c8811fce65d504fb566f15e2
Timestamp: 1749475715 Timestamp [UCT]: 2025-06-09 13:28:35 Age [y:d:h:m:s]: 00:155:20:23:01
Block: 1301370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109062 RingCT/type: yes/0
Extra: 01674570e1dcd49fbd224df0f54660792b51c69899c8811fce65d504fb566f15e2021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c21214db8878576103608ad1789b6ad2b8d81c4a9df356906f50406bcad9a4 0.600000000000 1788927 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": 1301380, "vin": [ { "gen": { "height": 1301370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c21214db8878576103608ad1789b6ad2b8d81c4a9df356906f50406bcad9a4" } } ], "extra": [ 1, 103, 69, 112, 225, 220, 212, 159, 189, 34, 77, 240, 245, 70, 96, 121, 43, 81, 198, 152, 153, 200, 129, 31, 206, 101, 213, 4, 251, 86, 111, 21, 226, 2, 17, 0, 0, 0, 8, 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