Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23ecf7a7c59846d399cc1f9694b1be2df39c38661e0d9d3b646b3a3ae33d9930

Tx prefix hash: 8a3707ab82e33ef939f0bb72778eca711ae0e6fb3461e2bfc18e429982cfc807
Tx public key: feed04fbdf373e9f6f2e072897ac4c9b819f7c4d7e759264f3e4629b1ea13893
Timestamp: 1705321740 Timestamp [UCT]: 2024-01-15 12:29:00 Age [y:d:h:m:s]: 01:070:17:48:13
Block: 935845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311642 RingCT/type: yes/0
Extra: 01feed04fbdf373e9f6f2e072897ac4c9b819f7c4d7e759264f3e4629b1ea138930211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 023b924ed32bd51aefa9ef0d25e171695236d597215b8808c13f962d1eda5206 0.600000000000 1393863 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": 935855, "vin": [ { "gen": { "height": 935845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "023b924ed32bd51aefa9ef0d25e171695236d597215b8808c13f962d1eda5206" } } ], "extra": [ 1, 254, 237, 4, 251, 223, 55, 62, 159, 111, 46, 7, 40, 151, 172, 76, 155, 129, 159, 124, 77, 126, 117, 146, 100, 243, 228, 98, 155, 30, 161, 56, 147, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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